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

Back
New CVE Detected

CVE-2026-86707 – Authentication Bypass (Admin Account Takeover) – Private Feed Key WordPress Plugin

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-86707 is a critical authentication bypass vulnerability in the Private Feed Key WordPress plugin, versions 0.1 and earlier. The plugin fails to properly validate the feedkey parameter used to authenticate feed requests, allowing unauthenticated remote attackers to impersonate any WordPress user — including administrators. The flaw carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: The plugin does not verify that the key supplied in a feed request is one it actually issued. Instead of performing a strict, per-user comparison, it matches the supplied value against any stored user metadata value, so a value copied or guessed from one context can be reused to authenticate as a different, arbitrary user.
  • Trigger conditions: An attacker submits a feed request containing a feedkey parameter value that matches any user metadata entry stored by the plugin; no valid credentials, session, or prior authentication are required.
  • Attack vector: Network-based (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction required (UI:N) — the vulnerability can be exploited remotely and automatically.
  • Impact: Successful exploitation allows an unauthenticated attacker to assume the identity of any user on the affected WordPress site, including administrators, resulting in full compromise of confidentiality, integrity, and availability of the site.

Affected software

  • Private Feed Key WordPress plugin, version 0.1 and all earlier versions

Severity

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

Mitigation and recommended actions

  • Immediate: No patched version of Private Feed Key has been released as of publication. Security teams should deactivate and uninstall the plugin until an official fix is available.
  • If no patch: As a network mitigation, block or restrict access to endpoints that accept the feedkey parameter (e.g., via WAF rules) and monitor for anomalous authentication activity or administrator logins originating from unexpected sources. Rotate credentials for any accounts (especially administrator accounts) on sites where this plugin is or was active, and review user activity logs for signs of unauthorized access.

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge