CVE-2022-34839

WP OAuth2 Server <= 1.0.1 - Authentication Bypass

2022-07-18 00:00
István Márton

Strategic Overview

Status
Unpatched
Affected Plugin
WP OAuth2 Server
Affected Version
<= 1.0.1
CVSS
7.3High
Weakness type
CWE-288 · Authentication Bypass Using an Alternate Path or Channel
CVE
CVE-2022-34839
View all WP OAuth2 Server vulnerabilities

At a glance

CVE-2022-34839 is a high-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the WP OAuth2 Server WordPress plugin, affecting versions <= 1.0.1. It carries a CVSS score of 7.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed July 2022, reported by István Márton.

Vulnerability Overview

The WP OAuth2 Server plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 1.0.1.

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-288: Authentication Bypass Using an Alternate Path or Channel

Reaching this weakness in WP OAuth2 Server <= 1.0.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 WP OAuth2 Server yet, so installs running <= 1.0.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