# CVE-2025-2110: WP Compress <= 6.30.15 - Authenticated (Subscriber+) Missing Authorization via Multiple Functions

> Authenticated subscribers can access and modify sensitive plugin settings due to missing capability checks in AJAX functions.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-jx2h-xcqm-jgfh

## What is CVE-2025-2110?

CVE-2025-2110 is a high-severity missing authorization vulnerability in aresit WP Compress – Instant Performance & Speed Optimization, published on 26 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-2110?

It affects 1 product.


Products: Wpcompress Wp Compress.

## How do I fix CVE-2025-2110?

No fix has been published for CVE-2025-2110 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-2110 being exploited?

There is no known exploitation of CVE-2025-2110 in the wild and no public exploit code.

## Other vulnerabilities in aresit WP Compress – Instant Performance & Speed Optimization

- [CVE-2023-6699](https://insights.sbomify.com/CVE-2023-6699/): WP Compress – Image Optimizer [All-In-One] <= 6.10.33 - Unauthenticated Directory Traversal via css (critical 9.1)
- [CVE-2024-1934](https://insights.sbomify.com/CVE-2024-1934/): WP Compress – Image Optimizer <= 6.11.08 - Missing Authorization to Unauthenticated CDN Modification (high 7.5)
- [CVE-2025-47546](https://insights.sbomify.com/CVE-2025-47546/): WordPress WP Compress plugin <= 6.30.30 - Cross Site Request Forgery (CSRF) Vulnerability (high 7.1)
- [CVE-2024-47384](https://insights.sbomify.com/CVE-2024-47384/): WordPress WP Compress plugin <= 6.20.13 - Reflected Cross Site Scripting (XSS) vulnerability (high 7.1)
- [CVE-2024-4445](https://insights.sbomify.com/CVE-2024-4445/): WP Compress – Image Optimizer [All-In-One] <= 6.20.01 - Missing Authorization (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2110 and fix it if it is affected.

What it is: CVE-2025-2110 is a high-severity missing authorization vulnerability in aresit WP Compress – Instant Performance & Speed Optimization, published on 26 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2110 in the wild and no public exploit code.

Affected product: aresit WP Compress – Instant Performance & Speed Optimization. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-2110/ (Markdown: https://insights.sbomify.com/CVE-2025-2110/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2110
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2110
- OSV: https://osv.dev/vulnerability/CVE-2025-2110

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-2110/
Summaries are generated and may contain mistakes; the official description above is the record.