CVE-2025-10753 identifies a missing authorization vulnerability (CWE-862) in the OAuth Single Sign On – SSO (OAuth Client) plugin for WordPress, maintained by cyberlord92. The vulnerability exists in all versions up to and including 6.26.14. The root cause is the lack of capability checks and authentication verification on the OAuth redirect functionality, specifically accessible via the 'oauthredirect' option parameter. An unauthenticated attacker can exploit this by sending crafted requests with the redirect_url parameter to set or modify the global redirect URL option. This unauthorized modification can alter the OAuth redirection flow, potentially redirecting users to attacker-controlled URLs after login attempts. The vulnerability is remotely exploitable without any authentication or user interaction, increasing its risk profile. The CVSS v3.1 score is 5.3 (medium), reflecting the ease of exploitation and impact limited to integrity (unauthorized configuration changes) without affecting confidentiality or availability. No patches or official fixes are currently linked, and no known exploits have been reported in the wild. The vulnerability affects any WordPress site using this plugin version, which is widely used for OAuth-based single sign-on integration.

The primary impact of CVE-2025-10753 is on the integrity of the OAuth Single Sign On configuration within affected WordPress sites. By allowing unauthenticated attackers to modify the global redirect URL, attackers can redirect users to malicious or phishing sites after login attempts, potentially facilitating credential theft or session hijacking through social engineering. While the vulnerability does not directly expose sensitive data or cause denial of service, the redirection manipulation can undermine user trust and lead to secondary attacks. Organizations relying on this plugin for authentication may face reputational damage, user account compromise, and increased risk of phishing campaigns targeting their user base. The ease of exploitation and lack of authentication requirements make this vulnerability a significant risk for any site using the affected plugin versions, especially those with high user traffic or sensitive user data. The absence of known exploits in the wild suggests limited current exploitation but does not preclude future attacks.

To mitigate CVE-2025-10753, organizations should immediately upgrade the OAuth Single Sign On – SSO (OAuth Client) plugin to a version where this vulnerability is fixed once available. In the absence of an official patch, administrators should restrict access to the 'oauthredirect' functionality by implementing web application firewall (WAF) rules that block unauthorized requests attempting to modify the redirect_url parameter. Additionally, review and harden WordPress site permissions to limit who can modify plugin options. Monitoring HTTP logs for suspicious requests targeting the oauthredirect parameter can help detect exploitation attempts. Consider temporarily disabling the plugin if OAuth SSO is not critical or replacing it with alternative, actively maintained SSO plugins that enforce proper authorization checks. Finally, educate users about phishing risks related to unexpected redirects and implement multi-factor authentication to reduce the impact of credential theft.