CVE-2022-4148

WP OAuth Server <= 4.2.5 - Authenticated (Subscriber+) Arbitrary Client Deletion (wo_ajax_remove_client)

2023-02-21 00:00
István Márton

Strategic Overview

Status
Patched in 4.3.0
Affected Plugin
WP OAuth Server (OAuth Authentication)
Affected Version
<= 4.2.5
CVSS
4.3Medium
Weakness type
CWE-863 · Incorrect Authorization
CVE
CVE-2022-4148
View all WP OAuth Server (OAuth Authentication) vulnerabilities

At a glance

CVE-2022-4148 is a medium-severity Incorrect Authorization vulnerability in the WP OAuth Server (OAuth Authentication) WordPress plugin, affecting versions <= 4.2.5. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.3.0; sites on affected versions should update now. Disclosed February 2023, reported by István Márton.

Vulnerability Overview

The WP OAuth Server plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the wo_ajax_remove_client() function in versions up to, and including, 4.2.5. This makes it possible for authenticated attackers with minimal permissions such as a subscriber to delete arbitrary clients.

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.

CWE-863: Incorrect Authorization

WP OAuth Server (OAuth Authentication) <= 4.2.5 carries this weakness at wo_ajax_remove_client(), and reaching it takes an account at Subscriber level or above. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.

The action runs for users the code intended to exclude, with the same effect as having no check at all. For WP OAuth Server (OAuth Authentication) the fix is 4.3.0: builds <= 4.2.5 are affected, anything from 4.3.0 onward is not.

Remediation

Update to version 4.3.0, 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: WP OAuth Server (OAuth Authentication) 4.3.0 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-4148https://www.wordfence.com/threat-intel/vulnerabilities/id/27da9458-ac19-4b4e-a14b-d1ba62e9e9eahttps://nvd.nist.gov/vuln/detail/CVE-2022-4148

Related records

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