CVE-2026-65520
Unauthenticated SQLi in WP OAuth Server plugin (<=6.2.0)
Is CVE-2026-65520 being exploited?
Not confirmed. CVE-2026-65520 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-65520?
CVE-2026-65520 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-65520?
Yes. A fix has been recorded for CVE-2026-65520. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-65520 affect?
CVE-2026-65520 affects WP OAuth Server plugin <=6.2.0, WordPress sites using WP OAuth Server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-65520?
Upgrade WP OAuth Server to the fixed version or remove plugin; apply WAF/filters immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can run SQL queries to exfiltrate/modify DB, create admin accounts, and achieve full WordPress site takeover.
Immediate action required
- affected<= 6.2.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.