Strategic Overview
- Status
- Patched in 4.0.1
- Affected Plugin
- WP OAuth Server ( Login with WordPress )
- Affected Version
<= 3.0.4- CVSS
- 9.8Critical
- Weakness type
- CWE-288 · Authentication Bypass Using an Alternate Path or Channel
- CVE
CVE-2022-34149
At a glance
CVE-2022-34149 is a critical-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the WP OAuth Server ( Login with WordPress ) WordPress plugin, affecting versions <= 3.0.4. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.0.1; sites on affected versions should update now. Disclosed August 2022, reported by István Márton.
Vulnerability Overview
The plugin WP OAuth Server for WordPress is vulnerable to Authentication Bypass in versions up to, and including, 3.0.4. This makes it possible for attackers to gain administrative access to affected sites.
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. 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 WP OAuth Server ( Login with WordPress ) <= 3.0.4 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. For WP OAuth Server ( Login with WordPress ) the fix is 4.0.1: builds <= 3.0.4 are affected, anything from 4.0.1 onward is not.
Remediation
Update to version 4.0.1, 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 ( Login with WordPress ) 4.0.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WP OAuth Server ( Login with WordPress )
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C