Wp CompressWordPress extension · Wpcompress
CVE-2025-2110
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 · uneditedThe WP Compress – Instant Performance & Speed Optimization plugin for WordPress is vulnerable to unauthorized access, modification, and loss of data due to missing capability checks on its on its AJAX functions in all versions up to, and including, 6.30.15. This makes it possible for authenticated attackers, with Subscriber-level access and above, to compromise the site in various ways depending on the specific function exploited - for example, by retrieving sensitive settings and configuration details, or by altering and deleting them, thereby disclosing sensitive information, disrupting the plugin’s functionality, and potentially impacting overall site performance.
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 confidenceThe WP Compress WordPress plugin (versions up to 6.30.15) lacks capability checks on AJAX endpoints, allowing any authenticated user with Subscriber-level access or higher to execute privileged AJAX functions. Attackers can retrieve, modify, or delete sensitive plugin settings and configuration data, potentially exposing site information and disrupting plugin functionality.
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.30.16CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Identify WP Compress plugin installationLocate the WP Compress plugin files in your WordPress installation (typically in /wp-content/plugins/wpcompress/ or similar). Check the main plugin file for the declared version number, or query the WordPress database plugins table for the installed version.Affected if The plugin is installed and the version listed is below 6.30.16
-
Verify plugin statusCheck whether the WP Compress plugin is currently activated on your WordPress site through the Plugins admin page or by querying the wp_options table for the active_plugins option.Affected if The plugin is installed with a vulnerable version AND is currently active on the site
-
Confirm user role configurationReview your WordPress user roles and permissions. Check if any Subscriber-level or higher user accounts exist on the site by accessing the Users admin page or querying the wp_usermeta table.Affected if Subscriber or higher-level user accounts exist on the site while the vulnerable plugin version is active
-
Audit AJAX endpoint accessibilityInspect the plugin AJAX handlers by examining the plugin PHP files for wp_ajax_ and wp_ajax_nopriv_ action hooks. Note which functions are registered without capability checks using current_user_can() or similar permission functions.Affected if AJAX endpoints are registered without proper capability validation and are accessible to authenticated users with Subscriber role or higher
-
Check for unauthorized configuration changesReview the WP Compress plugin settings in the WordPress admin dashboard under the plugin settings page. Compare current configuration against expected values, or inspect the wp_options table for wpcompress related entries for unexpected modifications.Affected if Settings have been altered, reset, or deleted without administrator action, or sensitive configuration data has been exposed
Your environment is affected if the WP Compress plugin version is below 6.30.16 and the plugin is active on your WordPress site with any authenticated user accounts having Subscriber-level access or higher.
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.30.16
Update the WP Compress plugin to version 6.30.16 or later which implements proper capability checks on AJAX functions. If no update is available, disable the plugin until a fix is released.
6.30.16
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate WP Compress in the plugin list
- Check the current version number to confirm it is below 6.30.16
- Click 'Update Now' if an update is available, or manually download version 6.30.16 from wordpress.org and reinstall
- Verify the plugin updated successfully to version 6.30.16
- Test that the plugin functionality remains intact after the update
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
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2110 — 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-2025-2110 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