dbcve.org
Wp CompressWordPress extension · Wpcompress

CVE-2025-2109

MEDIUM · 5.8 CVSS v3.1 Published 2025-03-25
Fix available
A fix is available. Upgrade to 6.30.16 or later.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WP Compress WordPress plugin before version 6.30.16 contains a Server-Side Request Forgery (SSRF) vulnerability in its init() function. Unauthenticated attackers can exploit this to make arbitrary web requests from the server, potentially accessing internal services or exfiltrating data.

MitigationUpdate the WP Compress plugin to version 6.30.16 or later. Until patched, consider deploying a WAF rule to block suspicious outbound requests and restrict the site's ability to make external requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp CompressWordPress extension
Affected:< 6.30.16

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if WP Compress plugin is installed
    Navigate to WordPress admin > Plugins and look for 'WP Compress' in the list of installed plugins, or check the /wp-content/plugins/ directory for a folder named 'wpcompress' or similar
    Affected if The plugin is not present in the installation
  2. Identify installed WP Compress version
    In WordPress admin > Plugins, find WP Compress and read the version number from the plugin details. Alternatively, open the main plugin file (typically wp-content/plugins/wpcompress/wp-compress.php or similar) and look for the 'Version' header in the plugin comment block
    Affected if Version is displayed as less than 6.30.16 or the Version header cannot be found (plugin may be outdated)
  3. Check plugin file for init() function exposure
    Locate the main plugin PHP file and search for a function named init() or __construct() that handles incoming requests. This function is where the SSRF vulnerability exists according to the CVE description
    Affected if An init() or similar initialization function exists that processes unauthenticated request parameters without validation
  4. Verify external request capability is enabled
    Check plugin settings in WordPress admin for WP Compress configuration options that enable external image processing, CDN connections, or API calls. The vulnerability allows arbitrary web requests, so any enabled external feature increases exposure
    Affected if External request features or API connections are enabled in the plugin settings

A user is affected if the WP Compress plugin is installed with a version lower than 6.30.16 and the plugin's initialization function is accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.30.16 or later
Fixed in 6.30.16
Interim mitigation

Update the WP Compress plugin to version 6.30.16 or later. Until patched, consider deploying a WAF rule to block suspicious outbound requests and restrict the site's ability to make external requests.

Recommended fix High confidence

6.30.16

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find WP Compress in the plugin list
  4. Check if the current version is below 6.30.16
  5. If update available, click 'Update Now' to upgrade to version 6.30.16
  6. Alternatively, manually download version 6.30.16 from wordpress.org and upload via Plugins > Add New > Upload Plugin
  7. Verify the plugin is running version 6.30.16 after updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wp Compress Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2109 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-2109 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data