OAuth Single Sign On – SSO (OAuth Client) <= 6.26.14 - Missing Authorization
Strategic Overview
- Status
- Patched in 6.26.15
- Affected Plugin
- OAuth Single Sign On – SSO (OAuth Client)
- Affected Version
<= 6.26.14- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-10753
At a glance
CVE-2025-10753 is a medium-severity Missing Authorization vulnerability in the OAuth Single Sign On WordPress plugin, affecting versions <= 6.26.14. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.26.15; sites on affected versions should update now. Disclosed February 2026, reported by Jonas Benjamin Friedli.
Vulnerability Overview
The OAuth Single Sign On – SSO (OAuth Client) plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 6.26.14. This is due to missing capability checks and authentication verification on the OAuth redirect functionality accessible via the 'oauthredirect' option parameter. This makes it possible for unauthenticated attackers to set the global redirect URL option via the redirect_url parameter granted they can access the site directly.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
OAuth Single Sign On <= 6.26.14 carries this weakness at oauthredirect, and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For OAuth Single Sign On the fix is 6.26.15: builds <= 6.26.14 are affected, anything from 6.26.15 onward is not.
Remediation
Update to version 6.26.15, 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.15 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
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.1CVE-2024-10111: OAuth Single Sign On – SSO Authentication Bypass
CVE-2024-10111 - 8.1CVE-2022-2133: OAuth Single Sign On – SSO Authentication Bypass
CVE-2022-2133 - 6.4OAuth Single Sign On – SSO (OAuth Client) <= 6.22.5 XSS
- 6.1Multiple miniOrange Plugins (Various Version) Reflected XSS
- 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