OAuth Single Sign On: A security weakness
OAuth Single Sign On is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
- Component
- OAuth Single Sign On
- Plugin slug
oauth-single-sign-on- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Jul 17, 2022
This CVE was published Jul 17, 2022 and is one of 3 known issues for this plugin.
Update, patch or deactivate.
Update OAuth Single Sign On 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 OAuth Single Sign On WordPress plugin before 6.22.6 doesn't validate that OAuth access token requests are legitimate, which allows attackers to log onto the site with the only knowledge of a user's email address.
NVD vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N