WP OAuth Server (OAuth Authentication) <= 4.2.5 -Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 4.3.0
- Affected Plugin
- WP OAuth Server (OAuth Authentication)
- Affected Version
<= 4.2.5- CVSS
- 5.4Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE pending
At a glance
This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP OAuth Server (OAuth Authentication) WordPress plugin, affecting versions <= 4.2.5. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.3.0; sites on affected versions should update now. Disclosed January 2023.
Vulnerability Overview
The WP OAuth Server plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.2.5. This is due to missing or incorrect nonce validation on several of its AJAX actions like wo_ajax_remove_self_generated_token. This makes it possible for unauthenticated attackers to remove generated tokens for users, via forged request granted they can trick a site user into performing an action such as clicking on a link.
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.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in WP OAuth Server (OAuth Authentication) <= 4.2.5 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. 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?
The attempt arrives as an ordinary request to WP OAuth Server (OAuth Authentication): WordSec's web application firewall inspects request payloads before WordPress loads them. 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.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WP OAuth Server (OAuth Authentication)
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C