CVE-2022-34155

OAuth Single Sign On – SSO (OAuth Client) <= 6.23.3 - Missing Authorization

2023-05-24 00:00
István Márton

Strategic Overview

Status
Patched in 6.23.4
Affected Plugin
OAuth Single Sign On – SSO (OAuth Client)
Affected Version
<= 6.23.3
CVSS
8.8High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2022-34155
View all OAuth Single Sign On – SSO (OAuth Client) vulnerabilities

At a glance

CVE-2022-34155 is a high-severity Missing Authorization vulnerability in the OAuth Single Sign On WordPress plugin, affecting versions <= 6.23.3. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 6.23.4; sites on affected versions should update now. Disclosed May 2023, reported by István Márton.

Vulnerability Overview

The OAuth Single Sign On – SSO (OAuth Client) plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on multiple AJAX functions in versions up to, and including, 6.23.3. This makes it possible for authenticated attackers with subscriber-level permissions to modify the plugin's settings, which could potentially be used to achieve privilege escalation.

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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

Reaching this weakness in OAuth Single Sign On <= 6.23.3 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 Single Sign On the fix is 6.23.4: builds <= 6.23.3 are affected, anything from 6.23.4 onward is not.

Remediation

Update to version 6.23.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 Single Sign On 6.23.4 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-34155https://www.wordfence.com/threat-intel/vulnerabilities/id/5d166a77-d57b-4827-96ca-b8eb423861f0https://nvd.nist.gov/vuln/detail/CVE-2022-34155

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C