OAuth Single Sign On – SSO (OAuth Client) <= 6.26.3 - Authentication Bypass
Strategic Overview
- Status
- Patched in 6.26.4
- Affected Plugin
- OAuth Single Sign On – SSO (OAuth Client)
- Affected Version
<= 6.26.3- CVSS
- 8.1High
- Weakness type
- CWE-287 · Improper Authentication
- CVE
CVE-2024-10111
At a glance
CVE-2024-10111 is a high-severity Improper Authentication vulnerability in the OAuth Single Sign On WordPress plugin, affecting versions <= 6.26.3. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 6.26.4; sites on affected versions should update now. Disclosed December 2024, reported by wesley (wcraft).
Vulnerability Overview
The OAuth Single Sign On – SSO (OAuth Client) plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 6.26.3. This is due to insufficient verification on the user being returned by the social login token. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the username and the user does not have an already-existing account for the service returning the token.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-287: Improper Authentication
Reaching this weakness in OAuth Single Sign On <= 6.26.3 takes a caller who can reach the endpoint. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.
An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For OAuth Single Sign On the fix is 6.26.4: builds <= 6.26.3 are affected, anything from 6.26.4 onward is not.
Remediation
Update to version 6.26.4, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: OAuth Single Sign On 6.26.4 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in OAuth Single Sign On – SSO (OAuth Client)
- 9.8CVE-2025-9485: OAuth Single Sign On – SSO Authentication Bypass
CVE-2025-9485 - 8.8CVE-2022-34155: OAuth Single Sign On – SSO Missing Authorization
CVE-2022-34155 - 6.4OAuth Single Sign On – SSO (OAuth Client) <= 6.22.5 XSS
- 6.1Multiple miniOrange Plugins (Various Version) Reflected XSS
- 5.3CVE-2025-10753: OAuth Single Sign On – SSO Missing Authorization
CVE-2025-10753 - 4.3CVE-2025-10752: OAuth Single Sign On – SSO (OAuth Client) CSRF
CVE-2025-10752 - 4.3CVE-2023-1092: OAuth Single Sign On – SSO (OAuth Client) CSRF
CVE-2023-1092 - 4.3CVE-2023-1093: OAuth Single Sign On – SSO (OAuth Client) CSRF
CVE-2023-1093
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C