CVE-2026-25370
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 · uneditedMissing Authorization vulnerability in AresIT WP Compress wp-compress-image-optimizer allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Compress: from n/a through <= 6.60.28.
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 confidenceThe WP Compress image optimizer WordPress plugin contains a missing authorization vulnerability that allows attackers to access functionality without proper capability checks. This appears to be a classic WordPress plugin authorization flaw where AJAX actions or admin functions lack wpnonce verification or current_user_can() capability checks, potentially allowing unauthenticated or low-privilege users to perform actions intended for administrators.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP Compress plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for the wp-compress-images folder, or list installed plugins via WP CLI: wp plugin list --status=active --format=csvAffected if WP Compress plugin is present and active in the WordPress installation
-
Determine installed WP Compress versionRead the main plugin file (wp-compress-images/plugin.php or similar) and locate the Version header, or use WP CLI: wp plugin get wp-compress-images --format=jsonAffected if The installed version matches or falls within the affected version range for this CVE (check against latest patched version when available)
-
Identify accessible AJAX endpointsExamine the plugin source code for registered AJAX actions (add_action('wp_ajax_...') and add_action('wp_ajax_nopriv_...') calls) in the plugin's main PHP filesAffected if AJAX actions are registered that handle sensitive operations without registered nonce verification or capability checks
-
Inspect AJAX handlers for authorization flawsReview the PHP functions hooked to AJAX actions for missing current_user_can() checks or missing wp_verify_nonce() / check_ajax_referer() callsAffected if Sensitive AJAX handlers (e.g., image optimization, settings changes, cache management) lack capability verification and process requests without proper authorization
-
Test unauthenticated access to admin functionsIf wp_ajax_nopriv_ hooks exist for sensitive operations, attempt to trigger them without authentication (e.g., via curl or Burp) to confirm if authorization is enforcedAffected if AJAX actions with wp_ajax_nopriv_ hooks execute privileged operations without verifying user identity or permissions
A user is affected if WP Compress is installed and its AJAX handlers or admin functions lack proper capability checks (current_user_can) and nonce verification, allowing unauthenticated or low-privilege users to trigger administrative actions.
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.
From vendor dataUpdate WP Compress to the latest version as soon as a patch is released. If no patch is available, disable the plugin or implement firewall rules to restrict access to the affected endpoints until a fix can be applied.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25370 — 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-2026-25370 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