Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-85681 – Unauthenticated Privilege Escalation / Site Takeover – WP Component WordPress Plugi

Be the first to know when new zero-days emerge:

Summary

CVE-2026-85681 is a critical improper privilege management vulnerability (CWE-269) affecting the WP Component WordPress plugin in versions up to and including 2.2.4. The plugin exposes an action to unauthenticated users without any capability or nonce checks, allowing attackers to overwrite arbitrary WordPress site options. On single-site installations, this can be leveraged to enable open user registration with a default role of administrator, resulting in full site takeover. The flaw has a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: One of the plugin’s AJAX/admin-ajax actions accepts an arbitrary option name and option value directly from the incoming request and writes it to the WordPress options table without verifying the requesting user’s capabilities or a valid nonce.
  • Trigger conditions: No authentication or user interaction is required; an attacker simply sends a crafted HTTP request to the exposed action.
  • Attack vector: Network — the vulnerable endpoint is reachable remotely over HTTP(S) with no prerequisites.
  • Impact: Arbitrary WordPress option overwrite. On single-site installs, attackers can set users_can_register to enabled and default_role to administrator, then self-register a new account with full administrative privileges — leading to complete compromise of the site (confidentiality, integrity, and availability all rated High impact).

Affected software

  • WP Component WordPress plugin, versions >= 0 and <= 2.2.4

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: No patched version has been released as of this writing. Site administrators should disable and remove the WP Component plugin until an official fix is published.
  • If the plugin must remain active: Restrict or block external access to the plugin’s admin-ajax action at the web server or WAF layer, closely monitor WordPress site options (particularly users_can_register and default_role) for unauthorized changes, and audit the users table for unexpected administrator accounts.
  • Ongoing: Monitor the plugin’s changelog/repository for a security release and apply it as soon as it becomes available.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge