WP Compress <= 6.30.15 - Unauthenticated Server-Side Request Forgery via init Function
Strategic Overview
- Status
- Patched in 6.30.16
- Affected Plugin
- WP Compress – Instant Performance & Speed Optimization
- Affected Version
<= 6.30.15- CVSS
- 5.8Medium
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2025-2109
At a glance
CVE-2025-2109 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the WP Compress WordPress plugin, affecting versions <= 6.30.15. It carries a CVSS score of 5.8 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.30.16; sites on affected versions should update now. Disclosed March 2025, reported by mikemyers.
Vulnerability Overview
The WP Compress – Instant Performance & Speed Optimization plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 6.30.15 via the init() function. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query information from internal services.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-918: Server-Side Request Forgery (SSRF)
WP Compress <= 6.30.15 carries this weakness at init(), and reaching it takes no account at all. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For WP Compress the fix is 6.30.16: builds <= 6.30.15 are affected, anything from 6.30.16 onward is not.
Remediation
Update to version 6.30.16, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Compress 6.30.16 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WP Compress – Instant Performance & Speed Optimization
- 9.8CVE-2026-73343: WP Compress RCE
CVE-2026-73343 - 9.1CVE-2023-6699: WP Compress Directory Traversal
CVE-2023-6699 - 8.8CVE-2025-2110: WP Compress <= 6.30.15 Missing Authorization
CVE-2025-2110 - 7.5CVE-2024-1934: WP Compress Unauthenticated CDN Modification
CVE-2024-1934 - 7.3CVE-2025-47479: WP Compress <= 6.30.30 Broken Authentication
CVE-2025-47479 - 6.5CVE-2026-17608: WP Compress CSRF to Arbitrary Options Deletion
CVE-2026-17608 - 6.5CVE-2024-4445: WP Compress Missing Authorization
CVE-2024-4445 - 6.1CVE-2026-9066: Compress <= 7.10.3 Reflected Cross-Site Scripting
CVE-2026-9066
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C