OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) <= 3.0.3 - Missing Authorization
Strategic Overview
- Status
- Patched in 3.0.4
- Affected Plugin
- OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO )
- Affected Version
<= 3.0.3- CVSS
- 7.3High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2022-3119
At a glance
CVE-2022-3119 is a high-severity Missing Authorization vulnerability in the OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) WordPress plugin, affecting versions <= 3.0.3. It carries a CVSS score of 7.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.0.4; sites on affected versions should update now. Disclosed August 2022, reported by István Márton.
Vulnerability Overview
The OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the save_oauthclient_config() function that is hooked via 'init' in versions up to, and including, 3.0.3. This makes it possible for unauthenticated attackers to modify the plugin's oAuth settings which could lead to unauthorized and high privileged access to a vulnerable site.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) <= 3.0.3 carries this weakness at init, and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) the fix is 3.0.4: builds <= 3.0.3 are affected, anything from 3.0.4 onward is not.
Remediation
Update to version 3.0.4, or a newer patched version
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. None of that substitutes for the fix: OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) 3.0.4 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO )
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C