WordPress security by component

OAuth Single Sign On – SSO (OAuth Client)

Plugin description

OAuth Single Sign On – SSO (OAuth Client) connects WordPress login and registration with external OAuth identity providers for single sign-on access.

OAuth Single Sign On – SSO (OAuth Client) (miniorange-login-with-eve-online-google-facebook) is a WordPress plugin with 7 published CVE records in this archive. The latest tracked vulnerability was published Sep 30, 2026; the highest published CVSS base score is 9.8.

Plugin slug: miniorange-login-with-eve-online-google-facebook

Latest vulnerability

CVE-2026-97274: OAuth Single Sign On – SSO (OAuth Client): Privilege escalation or authentication bypass

Unauthenticated Bypass Vulnerability in OAuth Single Sign On – SSO (OAuth Client) <= 7.1.2 versions. The export identifies a bypass but does not disclose the request path, bypassed check or account/data scope. The authoritative export does not identify the vulnerable endpoint, action, parameter or function, so the precise input-to-operation path cannot be established from this snapshot. The authoritative export identifies the fixed release as 7.1.3.

PublishedSep 30, 2026

Known safe version7.1.3

Published vulnerabilities for miniorange-login-with-eve-online-google-facebook
		Safe version
Sep 30, 2026	CVE-2026-97274 OAuth Single Sign On – SSO (OAuth Client): Privilege escalation or authentication bypass Unauthenticated Bypass Vulnerability in OAuth Single Sign On – SSO (OAuth Client) <= 7.1.2 versions. The export identifies a bypass but does not disclose the request path, bypassed check or account/data scope. The authoritative export does not identify the vulnerable endpoint, action, parameter or function, so the precise input-to-operation path cannot be established from this snapshot. The authoritative export identifies the fixed release as 7.1.3.	7.1.3	CVE9.8
Aug 13, 2026	CVE-2026-28008 miniOrange OAuth SSO trusts unverified Steam OpenID identities OAuth Single Sign On through 7.0.0 accepts a Steam OpenID callback and trusts attacker-controlled openid_claimed_id without asking the OpenID provider to validate the assertion. An unauthenticated attacker can therefore submit forged identity material across the login trust boundary. Version 7.0.1 adds mooauth_verify_openid_assertion() and performs the provider check_authentication round trip before accepting the identity.	7.0.1	CVE9.8
Feb 06, 2026	CVE-2025-10753 OAuth Single Sign On – SSO (OAuth Client): A security weakness OAuth Single Sign On – SSO (OAuth Client) is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.	See mitigation notes	CVE5.3
Oct 04, 2025	CVE-2025-9485 OAuth Single Sign On – SSO (OAuth Client): A security weakness OAuth Single Sign On – SSO (OAuth Client) is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.	See mitigation notes	CVE9.8
Sep 26, 2025	CVE-2025-10752 OAuth Single Sign On – SSO (OAuth Client): Cross-site request forgery OAuth Single Sign On – SSO (OAuth Client) is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.	See mitigation notes	CVE4.3
Dec 12, 2024	CVE-2024-10111 OAuth Single Sign On – SSO (OAuth Client): Privilege escalation or authentication bypass OAuth Single Sign On – SSO (OAuth Client) is affected by privilege escalation or authentication bypass. The vulnerable path is reachable without authentication. A successful request can grant permissions or access that the caller should not possess.	See mitigation notes	CVE8.1
Jul 18, 2023	CVE-2022-34155 OAuth Single Sign On – SSO (OAuth Client): Privilege escalation or authentication bypass OAuth Single Sign On – SSO (OAuth Client) is affected by privilege escalation or authentication bypass. Exposure depends on how the affected operation is made reachable by the site. A successful request can grant permissions or access that the caller should not possess.	See mitigation notes	CVE8.8

Data attribution: This product uses the NVD API but is not endorsed or certified by the NVD.

Vulnerability data licensing

CVE. Copyright © 1999–2026, The MITRE Corporation. MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE™). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

CWE. Copyright © 2006–2026, The MITRE Corporation. CWE™ is free to use by any organization or individual for any research, development, and/or commercial purposes, per these CWE Terms of Use. Accordingly, The MITRE Corporation hereby grants you a non-exclusive, royalty-free license to use CWE for research, development, and commercial purposes. Any copy you make for such purposes is authorized on the condition that you reproduce MITRE’s copyright designation and this license in any such copy.

CVSS. CVSS is owned and managed by FIRST.Org, Inc. (FIRST) and used by permission.

Source-record text is CVE/CNA content delivered through the NVD API. Fused summaries and remediation guidance are independently authored and are not attributed to NVD.

All other copyrights and trademarks are the property of their respective owners.

Full data sources, terms, and disclaimers