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

New CVE Detected

CVE-2026-87963 – Unauthenticated SQL Injection – Yo WordPress Plugin ≤1.3.1

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

Summary

CVE-2026-87963 is an unauthenticated SQL injection vulnerability in the Yo WordPress plugin, affecting versions 1.1 through 1.3.1. The plugin fails to sanitize or parameterize the username request parameter before using it in a SQL query, allowing remote, unauthenticated attackers to extract arbitrary database contents — including administrator password hashes. The flaw carries a CVSS v3.1 base score of 8.6 (High).

Technical details

  • Root cause: The plugin reads the username parameter from incoming requests and concatenates it directly into a SQL query without sanitization or parameterized queries, and the value is read before WordPress’s built-in escaping is applied.
  • Trigger conditions: No authentication or user interaction is required; an attacker only needs network access to a vulnerable site’s endpoint that processes the username parameter.
  • Attack vector: Network-based (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N).
  • Impact: Confidentiality impact is high (C:H) — successful exploitation allows extraction of arbitrary database contents, including administrator credentials/password hashes, which could enable full site takeover via credential reuse or password cracking. Integrity and availability are not directly impacted by the injection itself.

Affected software

  • Yo WordPress plugin, versions 1.1 through 1.3.1 (inclusive)

Severity

  • CVSS v3.1 Base Score: 8.6 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: As of this writing, no fixed version of the Yo plugin has been released. Security teams should treat this as an unpatched vulnerability.
  • Recommended interim actions:
    • Deactivate and remove the Yo plugin from any WordPress installation until a patched version is available.
    • If the plugin must remain active, restrict or block external access to the vulnerable endpoint(s) that process the username parameter via a WAF or reverse proxy rule filtering SQL metacharacters.
    • Monitor web server and database logs for anomalous requests containing SQL injection payloads in the username parameter.
    • Rotate administrator credentials and audit for signs of prior compromise if the plugin has been in use on internet-facing sites.
    • Continue to check for vendor updates and apply a patch immediately once released.

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