Security Resilience

CVE-2025-2110

Access Control in Wpcompress Wp Compress ≤ 6.30.16

Published
26 March 2025
Modified
11 August 2025
Patch / advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0046 39th percentile
Risk Priority 64 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-2110 is a high-severity Missing Authorization (CWE-862) vulnerability in Wpcompress Wp Compress. Its CVSS base score is 8.8 (High).

Operationally, ranked at the 39th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-25 (Reference Monitor) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-2110 affects the WP Compress – Instant Performance & Speed Optimization plugin for WordPress, specifically due to missing capability checks on its AJAX functions in all versions up to and including 6.30.15. This vulnerability, classified under CWE-862 (Missing Authorization), enables unauthorized access, modification, and loss of data. It carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), indicating high severity with network accessibility, low attack complexity, and requirements for low-privilege (Subscriber-level) authentication.

Authenticated attackers with Subscriber-level access or higher can exploit this over the network without user interaction. Depending on the targeted AJAX function, they can retrieve sensitive settings and configuration details, alter or delete them, leading to disclosure of confidential information, disruption of the plugin's functionality, and potential degradation of overall site performance.

Advisories, including the Wordfence threat intelligence report, highlight the need to update the plugin beyond version 6.30.15. The fix is detailed in WordPress plugin changeset 3254259, with vulnerable code visible in the 6.30.15 tag of ajax.class.php; practitioners should review the plugin's developer page for patched releases.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The 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,…

more

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.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-1934Same product: Wpcompress Wp Compress
CVE-2024-4445Same product: Wpcompress Wp Compress
CVE-2024-10533Shared CWE-862
CVE-2025-31757Shared CWE-862
CVE-2025-41338Shared CWE-862
CVE-2024-50459Shared CWE-862
CVE-2025-23930Shared CWE-862
CVE-2024-54466Shared CWE-862
CVE-2025-4179Shared CWE-862
CVE-2024-1129Shared CWE-862

Affected Assets

wpcompress
wp compress
≤ 6.30.16

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

AC-3 directly requires enforcement of authorization decisions on every access request, structurally eliminating missing authorization checks.

AC-24 mandates that access control decisions are applied to each request, preventing bypass of authorization logic.

AC-25 requires a tamperproof, always-invoked reference monitor that ensures authorization checks cannot be omitted.

AC-6 reduces the set of actions reachable without proper authorization, limiting blast radius of missing checks.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.5.18's provisioning, review, revocation and activation steps (incl. owner approval, SoD, timely removal on role/termination change) directly stop exploitation of missing authorization checks by ensuring no actor receives or retains rights to resources they should not access; the bounded remainder is that it cannot stop missing-authorization defects inside the enforcement mechanism itself once rights have been granted (e.g. flawed code that ignores the rights table).

blocks

A.8.3 directly mandates restricting access to information per policies via configuration, identity/group controls, isolation, and dynamic techniques that enforce authorization decisions, which squarely stops exploitation of missing authorization (CWE-862); the bounded remainder is non-access mechanisms such as path traversal or CSRF that are outside its scope per the AC-3/A01:2025 anchor.

blocks

Requiring formal authorization of every access request before rights are granted ensures that checks for required permissions are performed, preventing missing authorization checks from being introduced.

finds

By requiring competent outsiders to verify that every function enforces the need-to-know principle, the control lowers the likelihood that missing authorization checks persist undetected.

blocks

Requiring evidence of minimum security capabilities and acceptance testing ensures that missing or bypassed authorization checks are detected before the delivered software is accepted.

finds

Mandating read-only access or proxy execution by an authorized administrator ensures every requested operation is explicitly authorized before it occurs.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-862, a class-level weakness, and none of its children carries one either.

References