# CVE-2026-87963: Yo 1.1 - 1.3.1 - Unauthenticated SQL Injection via username Parameter

> Unauthenticated attackers can inject SQL via the username parameter to read arbitrary database contents, including administrator password hashes.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 20 Sep 2026
- **Also known as:** GHSA-vfmj-6hfh-5m4v

## What is CVE-2026-87963?

CVE-2026-87963 is a high-severity SQL injection vulnerability in Unknown Yo, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Yo WordPress plugin from 1.1 through 1.3.1 does not sanitize or parameterize the username request parameter before using it in a SQL query, and reads it before WordPress applies its request escaping, allowing unauthenticated attackers to perform SQL injection and read arbitrary database contents including administrator password hashes.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-87963?


## How do I fix CVE-2026-87963?

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

## Is CVE-2026-87963 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-87963 and fix it if it is affected.

What it is: CVE-2026-87963 is a high-severity SQL injection vulnerability in Unknown Yo, published on 17 Sep 2026. 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-2026-87963 in the wild and no public exploit code.

Affected product: Unknown Yo. 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-2026-87963/ (Markdown: https://insights.sbomify.com/CVE-2026-87963/index.md)
```

## Sources

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

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