WP REST API (WP API) < 1.2.1 - Sensitive Information Disclosure
Strategic Overview
- Status
- Patched in 1.2.1
- Affected Plugin
- WP REST API (WP API)
- Affected Version
< 1.2.1- CVSS
- 7.5High
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE pending
At a glance
This record tracks a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WP REST API (WP API) WordPress plugin, affecting versions < 1.2.1. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 1.2.1; sites on affected versions should update now. Disclosed April 2015.
Vulnerability Overview
The WP REST API (WP API) plugin for WordPress is vulnerable to Sensitive Data Exposure in versions up to, and including, 1.2. This could allow attackers to extract sensitive user or configuration data.
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.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in WP REST API (WP API) < 1.2.1 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For WP REST API (WP API) the fix is 1.2.1: builds < 1.2.1 are affected, anything from 1.2.1 onward is not.
Remediation
Update to version 1.2.1, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: WP REST API (WP API) 1.2.1 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Other vulnerabilities in WP REST API (WP API)
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C