dbcve.org
Wp CompressWordPress extension · Wpcompress

CVE-2025-47546

HIGH · 8.8 CVSS v3.1 Published 2025-05-07
Fix available
A fix is available. Upgrade to after 6.30.30 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in AresIT WP Compress wp-compress-image-optimizer allows Cross Site Request Forgery.This issue affects WP Compress: from n/a through <= 6.30.30.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the WP Compress Image Optimizer plugin versions up to 6.30.30 allows attackers to induce authenticated users to perform unintended actions by tricking them into visiting malicious pages or clicking links. The plugin lacks proper CSRF token validation on state-changing operations.

MitigationImplement anti-CSRF tokens (nonces) for all state-changing actions and verify the nonce on server-side processing. Consider adding SameSite cookie attributes as an additional defense layer.

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.30

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify WP Compress plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Compress' or 'Wp Compress Image Optimizer' in the list. Check if it shows as 'Active'.
    Affected if The plugin is installed and active.
  2. Check the installed version number
    In Plugins list, click the plugin name or view link to access the plugin details. Note the version number displayed (for example: 6.30.30, 6.30.25, etc.).
    Affected if The version number is 6.30.30 or lower.
  3. Identify state-changing plugin actions
    Review the plugin source code in wp-content/plugins/wp-compress-image-optimizer/ directory. Look for PHP files handling form submissions, AJAX endpoints, or URL parameters that modify plugin settings, trigger image processing, or change plugin state.
    Affected if State-changing operations exist in the plugin without corresponding nonce verification code.
  4. Inspect for missing nonce validation
    In the identified state-changing code files, search for calls to check_admin_referer, wp_verify_nonce, or verify_nonce. Determine if these verification functions are present and properly implemented before any state-modifying database or configuration changes.
    Affected if State-changing functions execute without prior nonce/token verification.
  5. Check for SameSite cookie attribute
    If the plugin sets cookies (check for setcookie or setrawcookie functions in the plugin code), verify whether the SameSite attribute is configured on cookie definitions.
    Affected if SameSite attribute is not set on cookies, leaving them vulnerable to CSRF exploits.

You are affected if the WP Compress Image Optimizer plugin is installed at version 6.30.30 or lower AND contains state-changing operations that lack CSRF nonce verification.

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.

From vendor data
Upgrade available Upgrade to a release after 6.30.30
Interim mitigation

Implement anti-CSRF tokens (nonces) for all state-changing actions and verify the nonce on server-side processing. Consider adding SameSite cookie attributes as an additional defense layer.

Fix this in Wp Compress Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47546 — 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-47546 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