WordPress Single Sign-On (SSO): A security weakness
WordPress Single Sign-On (SSO) is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.
- Component
- WordPress Single Sign-On (SSO)
- Plugin slug
wordpress-single-sign-on-sso- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Jun 12, 2025
This CVE was published Jun 12, 2025 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update WordPress Single Sign-On (SSO) to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The WordPress Single Sign-On (SSO) plugin for WordPress is vulnerable to unauthorized access due to a misconfigured capability check on a function in all versions up to, and including, the *.5.3 versions of the plugin. This makes it possible for unauthenticated attackers to extract sensitive data including site content that has been restricted to certain users and/or roles.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N