CVE-2025-11007

CE21 Suite 2.2.1 - 2.3.1 - Missing Authorization to Unauthenticated Privilege Escalation via Plugin Settings Update

2025-11-03 15:23
kr0d

Strategic Overview

Status
Unpatched
Affected Plugin
CE21 Suite
Affected Version
2.2.1 – 2.3.1
CVSS
9.8Critical
Weakness type
CWE-306 · Missing Authentication for Critical Function
CVE
CVE-2025-11007
View all CE21 Suite vulnerabilities

At a glance

CVE-2025-11007 is a critical-severity Missing Authentication for Critical Function vulnerability in the CE21 Suite WordPress plugin, affecting versions 2.2.1 – 2.3.1. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed November 2025, reported by kr0d.

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-306: Missing Authentication for Critical Function

The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C