Simple Single Sign On <= 4.1.1 - Insecure OAuth Implementation to Authentication Bypass
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Simple Single Sign On
- Affected Version
<= 4.1.1- CVSS
- 8.1High
- Weakness type
- CWE-288 · Authentication Bypass Using an Alternate Path or Channel
- CVE
CVE-2022-2083
At a glance
CVE-2022-2083 is a high-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the Simple Single Sign On WordPress plugin, affecting versions <= 4.1.1. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed June 2022, reported by István Márton.
Vulnerability Overview
The Simple Single Sign On plugin for WordPress is vulnerable to authorization bypass due to insecurely configured OAuth in versions up to, and including, 4.1.1 which allows attackers to retrieve client access_tokens that can be used to authenticate to a vulnerable site. This makes it possible unauthenticated attackers to gain unauthorized access to vulnerable web servers.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-288: Authentication Bypass Using an Alternate Path or Channel
Reaching this weakness in Simple Single Sign On <= 4.1.1 takes a caller who can reach the endpoint. Authentication bypass through an alternate path means the application has a second route to a protected action that skips the checks the primary route performs.
The protection on the main path becomes irrelevant, because the attacker simply uses the route that never asks. No fixed build of this plugin is recorded for Simple Single Sign On yet, so installs running <= 4.1.1 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C