WordPress security by component
Zippy
Plugin description
Zippy is a WordPress component with 5 published CVE records in this archive. The latest tracked vulnerability was published Oct 22, 2025; the highest CVE/CNA score is 9.1.
Plugin slug:
zippyLatest vulnerability
CVE-2025-52758: Zippy: Dangerous file upload
Zippy is affected by dangerous file upload. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can place attacker-controlled executable content on the server and may lead to full site compromise.
| Safe version |
|
||
|---|---|---|---|
| Oct 22, 2025 |
CVE-2025-52758
Zippy: Dangerous file upload
Zippy is affected by dangerous file upload. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can place attacker-controlled executable content on the server and may lead to full site compromise.
|
See mitigation notes |
CVE9.1
NVDPending
|
| Dec 13, 2024 |
CVE-2023-34381
Zippy: A security weakness
Zippy is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE5.3
NVDPending
|
| Mar 21, 2024 |
CVE-2024-27964
Zippy: Dangerous file upload
Zippy is affected by dangerous file upload. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can place attacker-controlled executable content on the server and may lead to full site compromise.
|
See mitigation notes |
CVE8.8
NVD8.8
|
| Dec 28, 2023 |
CVE-2023-36381
Zippy: Code execution
Zippy is affected by code execution. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can run attacker-controlled code in the WordPress hosting account.
|
See mitigation notes |
CVE6.6
NVD8.8
|
| Nov 30, 2023 |
CVE-2023-26533
Zippy: A security weakness
Zippy is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE6.5
NVD6.5
|