# CVE-2025-11008: CE21 Suite <= 2.3.1 - Unauthenticated Sensitive Information Exposure to Privilege Escalation

> Unauthenticated attackers can extract sensitive credentials from log files to take over accounts, including administrators, if the custom authentication feature was used.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Nov 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-p3wr-7qrc-fwp9

## What is CVE-2025-11008?

CVE-2025-11008 is a critical vulnerability in ce21com CE21 Suite, published on 4 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The CE21 Suite plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.3.1 via the log file. This makes it possible for unauthenticated attackers to extract sensitive data including authentication credentials, which can be used to log in as other users as long as they have used the plugin's custom authentication feature before. This may include administrators, which makes a complete site takeover possible.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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


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

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

## Is CVE-2025-11008 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-11008 is a critical vulnerability in ce21com CE21 Suite, published on 4 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-11008 in the wild and no public exploit code.

Affected product: ce21com CE21 Suite. 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-11008/ (Markdown: https://insights.sbomify.com/CVE-2025-11008/index.md)
```

## Sources

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

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