CVE-2025-2109 json
WP Compress <= 6.30.15 - Unauthenticated Server-Side Request Forgery via init Function
published last yr. modified 4mo ago also EUVD-2025-8078
- cvss
- 5.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 34%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- wpcompress wp_compress 6.30.16
Is CVE-2025-2109 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N |
Affected products
- aresit WP Compress – Instant Performance & Speed Optimization
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
- Technology feeds
References
-
wordfence.com
/threat-intel/vulnerabilities/id/10b9d703-de9d-472a-bdfb-bc9a41bf375e?source=cve
third-party-advisory
-
plugins.trac.wordpress.org
/browser/wp-compress-image-optimizer/tags/6.30.15/wp-compress-core.php#L994
product
-
wordpress.org
/plugins/wp-compress-image-optimizer/#developers
release-notes
-
plugins.trac.wordpress.org
/changeset/3254259/
product
Sources
- CVE List CVE-2025-2109
- NVD CVE-2025-2109
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.