CVE-2025-9485: CWE-347 Improper Verification of Cryptographic Signature in cyberlord92 OAuth Single Sign On – SSO (OAuth Client)
The OAuth Single Sign On – SSO (OAuth Client) plugin for WordPress is vulnerable to Improper Verification of Cryptographic Signature in versions up to, and including, 6.26.12. This is due to the plugin performing unsafe JWT token processing without verification or validation in the `get_resource_owner_from_id_token` function. This makes it possible for unauthenticated attackers to bypass authentication and gain access to any existing user account - including administrators in certain configurations - or to create arbitrary subscriber-level accounts.
AI Analysis
Technical Summary
CVE-2025-9485 is a critical security vulnerability identified in the OAuth Single Sign On – SSO (OAuth Client) plugin for WordPress, maintained by cyberlord92. The vulnerability stems from improper verification of cryptographic signatures (CWE-347) in JSON Web Tokens (JWTs) processed by the plugin's get_resource_owner_from_id_token function. Specifically, the plugin fails to validate the JWT signature, allowing attackers to craft malicious tokens that the plugin accepts as valid. This flaw enables unauthenticated attackers to bypass authentication mechanisms entirely, granting them access to any existing user account on the WordPress site. In certain configurations, attackers can escalate privileges to administrator level, while in others, they can create arbitrary subscriber-level accounts. The vulnerability affects all versions up to and including 6.26.12. The CVSS v3.1 base score of 9.8 reflects the critical nature of the flaw, with an attack vector over the network, no required privileges or user interaction, and full impact on confidentiality, integrity, and availability of the affected systems. Although no known exploits have been observed in the wild, the vulnerability's characteristics make it highly exploitable. The lack of signature verification in JWT processing is a fundamental cryptographic error, undermining the trust model of OAuth-based authentication. This vulnerability poses a severe risk to WordPress sites using this plugin for Single Sign-On, potentially leading to unauthorized access, data breaches, and full site compromise.
Potential Impact
For European organizations, this vulnerability represents a significant threat to the security of WordPress-based web applications that utilize the OAuth Single Sign On – SSO (OAuth Client) plugin. Unauthorized access to user accounts, especially administrator accounts, can lead to full site compromise, data theft, defacement, or use of the site as a platform for further attacks. The ability to create arbitrary subscriber accounts also facilitates persistent footholds and lateral movement within the application environment. Given the widespread use of WordPress across Europe for corporate websites, e-commerce, and internal portals, exploitation could result in reputational damage, regulatory non-compliance (e.g., GDPR violations due to data breaches), and financial losses. The critical severity and ease of exploitation mean that attackers can operate remotely without authentication or user interaction, increasing the risk of automated mass exploitation campaigns targeting vulnerable sites across Europe. Organizations in sectors with high-value targets, such as finance, healthcare, and government, are particularly at risk due to the potential impact on sensitive data and services.
Mitigation Recommendations
Immediate mitigation involves updating the OAuth Single Sign On – SSO (OAuth Client) plugin to a patched version once released by the vendor. Until a patch is available, organizations should consider disabling the plugin or the SSO functionality to prevent exploitation. Implementing Web Application Firewall (WAF) rules to detect and block malformed or unsigned JWT tokens can provide interim protection. Conduct thorough audits of user accounts for unauthorized creations or privilege escalations. Enforce multi-factor authentication (MFA) on all administrator accounts to reduce the impact of compromised credentials. Review and restrict OAuth client configurations to minimize exposure. Monitor logs for suspicious authentication attempts or unusual token usage patterns. Additionally, organizations should educate administrators on the risks of using unverified third-party plugins and establish a process for timely vulnerability management and patching. Network segmentation and limiting administrative access to trusted IPs can further reduce the attack surface.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Poland, Sweden
CVE-2025-9485: CWE-347 Improper Verification of Cryptographic Signature in cyberlord92 OAuth Single Sign On – SSO (OAuth Client)
Description
The OAuth Single Sign On – SSO (OAuth Client) plugin for WordPress is vulnerable to Improper Verification of Cryptographic Signature in versions up to, and including, 6.26.12. This is due to the plugin performing unsafe JWT token processing without verification or validation in the `get_resource_owner_from_id_token` function. This makes it possible for unauthenticated attackers to bypass authentication and gain access to any existing user account - including administrators in certain configurations - or to create arbitrary subscriber-level accounts.
AI-Powered Analysis
Technical Analysis
CVE-2025-9485 is a critical security vulnerability identified in the OAuth Single Sign On – SSO (OAuth Client) plugin for WordPress, maintained by cyberlord92. The vulnerability stems from improper verification of cryptographic signatures (CWE-347) in JSON Web Tokens (JWTs) processed by the plugin's get_resource_owner_from_id_token function. Specifically, the plugin fails to validate the JWT signature, allowing attackers to craft malicious tokens that the plugin accepts as valid. This flaw enables unauthenticated attackers to bypass authentication mechanisms entirely, granting them access to any existing user account on the WordPress site. In certain configurations, attackers can escalate privileges to administrator level, while in others, they can create arbitrary subscriber-level accounts. The vulnerability affects all versions up to and including 6.26.12. The CVSS v3.1 base score of 9.8 reflects the critical nature of the flaw, with an attack vector over the network, no required privileges or user interaction, and full impact on confidentiality, integrity, and availability of the affected systems. Although no known exploits have been observed in the wild, the vulnerability's characteristics make it highly exploitable. The lack of signature verification in JWT processing is a fundamental cryptographic error, undermining the trust model of OAuth-based authentication. This vulnerability poses a severe risk to WordPress sites using this plugin for Single Sign-On, potentially leading to unauthorized access, data breaches, and full site compromise.
Potential Impact
For European organizations, this vulnerability represents a significant threat to the security of WordPress-based web applications that utilize the OAuth Single Sign On – SSO (OAuth Client) plugin. Unauthorized access to user accounts, especially administrator accounts, can lead to full site compromise, data theft, defacement, or use of the site as a platform for further attacks. The ability to create arbitrary subscriber accounts also facilitates persistent footholds and lateral movement within the application environment. Given the widespread use of WordPress across Europe for corporate websites, e-commerce, and internal portals, exploitation could result in reputational damage, regulatory non-compliance (e.g., GDPR violations due to data breaches), and financial losses. The critical severity and ease of exploitation mean that attackers can operate remotely without authentication or user interaction, increasing the risk of automated mass exploitation campaigns targeting vulnerable sites across Europe. Organizations in sectors with high-value targets, such as finance, healthcare, and government, are particularly at risk due to the potential impact on sensitive data and services.
Mitigation Recommendations
Immediate mitigation involves updating the OAuth Single Sign On – SSO (OAuth Client) plugin to a patched version once released by the vendor. Until a patch is available, organizations should consider disabling the plugin or the SSO functionality to prevent exploitation. Implementing Web Application Firewall (WAF) rules to detect and block malformed or unsigned JWT tokens can provide interim protection. Conduct thorough audits of user accounts for unauthorized creations or privilege escalations. Enforce multi-factor authentication (MFA) on all administrator accounts to reduce the impact of compromised credentials. Review and restrict OAuth client configurations to minimize exposure. Monitor logs for suspicious authentication attempts or unusual token usage patterns. Additionally, organizations should educate administrators on the risks of using unverified third-party plugins and establish a process for timely vulnerability management and patching. Network segmentation and limiting administrative access to trusted IPs can further reduce the attack surface.
Affected Countries
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-08-26T08:59:36.029Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68e0877c11971642e85b3483
Added to database: 10/4/2025, 2:33:32 AM
Last enriched: 10/11/2025, 8:43:38 AM
Last updated: 1/7/2026, 4:19:06 AM
Views: 245
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-20893: Origin validation error in Fujitsu Client Computing Limited Fujitsu Security Solution AuthConductor Client Basic V2
HighCVE-2025-14891: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in ivole Customer Reviews for WooCommerce
MediumCVE-2025-14059: CWE-73 External Control of File Name or Path in roxnor EmailKit – Email Customizer for WooCommerce & WP
MediumCVE-2025-12648: CWE-552 Files or Directories Accessible to External Parties in cbutlerjr WP-Members Membership Plugin
MediumCVE-2025-14631: CWE-476 NULL Pointer Dereference in TP-Link Systems Inc. Archer BE400
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.