Wp CompressWordPress extension · Wpcompress
CVE-2024-32106
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in WP Compress WP Compress – Image Optimizer [All-In-One].This issue affects WP Compress – Image Optimizer [All-In-One]: from n/a through 6.10.35.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in WP Compress WordPress plugin (versions through 6.10.35). The plugin fails to properly validate anti-CSRF tokens (nonces) on state-changing operations, allowing attackers to trick authenticated administrators into unknowingly performing actions such as modifying plugin settings or triggering image optimization processes.
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
< 6.11.01CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate WP Compress plugin installationNavigate to wp-content/plugins/ directory and identify the wp-compress plugin folder, or check via WordPress admin under Plugins > Installed PluginsAffected if The WP Compress plugin is present in the plugins directory
-
Identify installed plugin versionOpen the main plugin file (typically wp-compress.php or similar in the plugin root) and locate the 'Version' field in the plugin header comment at the top of the fileAffected if The version number displayed is less than 6.11.01 (e.g., 6.10.35, 6.10.30, etc.)
-
Inspect form handlers for nonce verificationExamine PHP files handling admin actions (look for functions processing form submissions or AJAX requests). Search for wp_verify_nonce, check_admin_referer, or wp_nonce_field calls within these handler filesAffected if Form handling code exists but lacks wp_verify_nonce or check_admin_referer validation calls
-
Review AJAX action handlersLocate files registering add_action calls for 'wp_ajax_' hooks. Open these files and check if the callback functions validate nonces before processing state-changing requestsAffected if AJAX handlers process requests without verifying nonce tokens
You are affected if the WP Compress plugin is installed with a version below 6.11.01 and the plugin lacks nonce validation in its form or AJAX handlers.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.11.01
Implement WordPress nonce verification (wp_verify_nonce/check_admin_referer) on all form submissions and AJAX actions within the plugin, and add nonce fields to all relevant forms.
6.11.01 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate 'WP Compress – Image Optimizer [All-In-One]' in the plugin list
- Check the current version number to confirm it is below 6.11.01
- Click 'Update now' if an update is available, or manually download version 6.11.01 or later from the WordPress plugin repository
- If manual update: click 'Upload Plugin' at the top of the Plugins page, upload the new version zip file, and click 'Install Now'
- After update completes, click 'Activate Plugin' if needed
- Verify the plugin is running version 6.11.01 or newer under Plugins > Installed Plugins
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Compress
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32106 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-32106 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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