# CVE-2025-11007: CE21 Suite 2.2.1 - 2.3.1 - Missing Authorization to Unauthenticated Privilege Escalation via Plugin Settings Update

> Unauthenticated attackers can update plugin settings to create admin accounts due to missing capability checks in the CE21 Suite WordPress plugin.

- **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:** 4 Nov 2025
- **Also known as:** GHSA-5m5x-66vw-r2rp

## What is CVE-2025-11007?

CVE-2025-11007 is a critical missing authorization 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 unauthorized plugin settings update due to a missing capability check on the wp_ajax_nopriv_ce21_single_sign_on_save_api_settings AJAX action in versions 2.2.1 to 2.3.1. This makes it possible for unauthenticated attackers to update the plugin's API settings including a secret key used for authentication. This allows unauthenticated attackers to create new admin accounts on an affected site.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2025-11007 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-11007 is a critical missing authorization 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-11007 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-11007/ (Markdown: https://insights.sbomify.com/CVE-2025-11007/index.md)
```

## Sources

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

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