WordPress REST API Authentication <= 2.4.0 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 2.4.1
- Affected Plugin
- JWT Authentication for WP REST APIs
- Affected Version
<= 2.4.0- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2022-45073
At a glance
CVE-2022-45073 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the JWT Authentication for WP REST APIs WordPress plugin, affecting versions <= 2.4.0. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.4.1; sites on affected versions should update now. Disclosed November 2022, reported by István Márton.
Vulnerability Overview
The WordPress REST API Authentication plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.4.0. This is due to missing or incorrect nonce validation on the 'save_temporary_data' function. This makes it possible for unauthenticated attackers to make plugin settings changes via a forged request granted they can trick a site administrator 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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
JWT Authentication for WP REST APIs <= 2.4.0 carries this weakness at save_temporary_data, and reaching it 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 JWT Authentication for WP REST APIs the fix is 2.4.1: builds <= 2.4.0 are affected, anything from 2.4.1 onward is not.
Remediation
Update to version 2.4.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to JWT Authentication for WP REST APIs: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: JWT Authentication for WP REST APIs 2.4.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in JWT Authentication for WP REST APIs
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C