Unauthenticated SQL injection via unparameterized username
Published Sep 17, 2026 · Updated Sep 20, 2026
SQL injection in the Yo WordPress plugin 1.1 through 1.3.1 allows remote attackers to read arbitrary database contents via the username parameter. The plugin reads the parameter before WordPress applies request escaping, then inserts it into a SQL query without sanitization or parameterization. No authentication is required, and successful exploitation exposes database records, including administrator password hashes, without granting database writes.
Summary
What happened
SQL injection in the Yo WordPress plugin 1.1 through 1.3.1 allows remote attackers to read arbitrary database contents via the username parameter. The plugin reads the parameter before WordPress applies request escaping, then inserts it into a SQL query without sanitization or parameterization. No authentication is required, and successful exploitation exposes database records, including administrator password hashes, without granting database writes.
The record
- CVE
- CVE-2026-87963
- Published
- Sep 17, 2026
- Updated
- Sep 20, 2026
- Vendor
- Paul Molluzzo
- Product
- Yo
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.1 <=1.3.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started