Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress site running WP OAuth Server
-
DeliverySend crafted request to OAuth endpoint
-
ExploitInject SQL into vulnerable parameter
-
ExecutionExtract user and token data from database
-
ImpactExfiltrate credentials for account takeover
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires only that the WP OAuth Server plugin (≤6.2.0) be installed and active on a network-reachable WordPress site, with its OAuth endpoints exposed as in a normal deployment; the CVSS vector AV:N/AC:L/PR:N/UI:N indicates no authentication, no user interaction, and no special configuration is needed to reach the injectable request handler. The primary limiting factor is that the site must actually run this specific miniOrange plugin at a vulnerable version - sites not using WP OAuth Server, or those that have restricted the OAuth endpoints behind a proxy/WAF, are not exposed. No default-off feature toggle is documented in the provided data. |
| Impact | The CVSS vector (AV:N/AC:L/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated attack with no user interaction - the top of the exploitability range, driving the 9.3 critical rating. Impact is skewed to confidentiality (C:H) with only limited availability (A:L) and no integrity impact (I:N), which fits a data-exfiltration-style SQLi rather than authentication bypass or full DB takeover; the changed scope (S:C) reflects that the plugin's queries can expose broader WordPress database contents. No EPSS score, KEV listing, POC, or SSVC decision data was provided, so real-world exploitation velocity cannot be quantified from this input. The absence of KEV/POC signals means this is a high-severity-by-vector finding whose actual exploitation likelihood is unconfirmed - treat as a priority patch given unauthenticated reach, but note the risk rating rests on the vector alone. |
| Exploit ScenarioDerived | A remote attacker with no account sends a crafted HTTP request to the plugin's OAuth endpoint with a malicious SQL payload in a vulnerable parameter, causing the injected query to run against the WordPress database. The attacker uses UNION-based or blind techniques to extract user records, password hashes, and OAuth secrets. No public exploit code has been identified, but the low complexity and unauthenticated vector make weaponization straightforward once endpoint details are known. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 06, 2026
SQL injection in the miniOrange WP OAuth Server WordPress plugin (all versions up to and including 6.2.0) lets remote unauthenticated attackers inject arbitrary SQL through the plugin's OAuth request handling, per CVSS:3.1 PR:N. The flaw carries a critical 9.3 score with a changed-scope confidentiality impact, meaning attacker-controlled queries can reach data beyond the intended authorization boundary. Reported by Patchstack (CVE-2026-65520 / EUVD-2026-53969); no public exploit identified at time of analysis.
RemediationAI
Upgrade the WP OAuth Server plugin to a release later than 6.2.0 once the vendor publishes it; released patched version is not independently confirmed from the provided data, so verify the fixed version against the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/miniorange-oauth-20-server/vulnerability/wordpress-wp-oauth-server-plugin-6-2-0-sql-injection-vulnerability) and the miniOrange changelog before deploying. Until a patched version is confirmed, restrict access to the plugin's OAuth endpoints with a WAF rule targeting SQL-injection patterns on the OAuth request/authorize/token parameters, or place the OAuth IdP behind IP allowlisting or authentication at the reverse proxy - noting this can break legitimate third-party OAuth clients that need public endpoint access. If OAuth SSO is not actively used, deactivating the plugin removes the exposed attack surface entirely.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
WP OAuth Server (cpe:2.3:a:miniorange:wp_oauth_server) is a WordPress plugin that turns a WordPress site into an OAuth 2.0 / OpenID Connect identity provider, issuing tokens and handling authorization endpoints for connected applications. The root cause is CWE-89 (SQL Injection): user-supplied input reaching an OAuth-related endpoint is concatenated into a SQL statement without proper parameterization or sanitization, so crafted input alters query structure. Because OAuth authorize/token endpoints are exposed to unauthenticated clients by design, the injectable surface is reachable pre-authentication, which is consistent with the PR:N metric.
Know when Wp Oauth Server gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
Unauthenticated network-reachable SQLi (AV:N/AC:L/PR:N/UI:N) enabling database read (C:H); no integrity/availability change and DB queries stay in-scope, so I:N/A:N/S:U.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated SQL Injection in WP OAuth Server <= 6.2.0 versions.
Executive ViewAI
The miniOrange WP OAuth Server WordPress plugin (versions ≤6.2.0) contains a critical SQL injection vulnerability (CVE-2026-65520, CVSS 9.3) that allows unauthenticated remote attackers to bypass authorization controls and exfiltrate database contents. Any WordPress site running this plugin faces immediate risk of total database compromise, including customer data, credentials, and sensitive business information.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Remove plugin from all systems immediately; (2) If operational continuity requires the plugin, implement Web Application Firewall rules to block OAuth request handlers; (3) Restrict database user privileges to minimum necessary scope and role-based permissions; (4) Enable real-time database activity monitoring and alerting for unusual or high-volume queries; (5) Monitor miniOrange security advisories and vendor communication channels for patch availability.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
More in Wp Oauth Server
View allThe WP OAuth Server (OAuth Authentication) WordPress plugin before 3.4.2 does not have CSRF check when regenerating secr
Authentication Bypass vulnerability in miniOrange WP OAuth Server plugin <= 3.0.4 at WordPress. Rated critical severity
The WP OAuth Server (OAuth Authentication) WordPress plugin before 4.2.2 does not sanitize and escape Client IDs, which
Missing authorization in the miniOrange WP OAuth Server WordPress plugin (all versions through 6.4.0) allows remote unau
URL Redirection to Untrusted Site ('Open Redirect') vulnerability in WP OAuth Server OAuth Server.3.3. Rated medium seve
EUVD-2026-53969
GHSA-75cj-86wv-m74j
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB