CVE-2025-10753
Unauthorized Access in WordPress OAuth SSO via Redirect URL
Publication date: 2026-02-06
Last updated on: 2026-02-06
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| miniorange | oauth_single_sign_on | to 6.26.14 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The OAuth Single Sign On – SSO (OAuth Client) plugin for WordPress has a vulnerability in all versions up to and including 6.26.14. This vulnerability arises because the plugin does not properly check user capabilities or verify authentication when handling the OAuth redirect functionality via the 'oauthredirect' option parameter.
As a result, unauthenticated attackers who can directly access the site can exploit this flaw to set the global redirect URL option by manipulating the redirect_url parameter.
How can this vulnerability impact me? :
This vulnerability allows unauthenticated attackers to change the global redirect URL used by the OAuth Single Sign On plugin. This could lead to unauthorized redirection of users to malicious sites.
While the vulnerability does not directly impact confidentiality or availability, it can impact the integrity of the authentication flow by enabling attackers to redirect users without proper authorization.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
The vulnerability affects all versions of the OAuth Single Sign On – SSO (OAuth Client) plugin for WordPress up to and including 6.26.14.
To mitigate this vulnerability, you should immediately update the plugin to a version later than 6.26.14, as the vulnerability is fixed in versions after this.
Since the vulnerability allows unauthenticated attackers to set the global redirect URL via the redirect_url parameter, restricting direct access to the vulnerable OAuth redirect functionality or disabling the plugin until an update can be applied may also help reduce risk.