ACF to REST API <= 3.2.0 - Insecure direct object reference via permalinks manipulation
Strategic Overview
- Status
- Patched in 3.3.0
- Affected Plugin
- ACF to REST API
- Affected Version
<= 3.2.0- CVSS
- 7.5High
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2020-13700
At a glance
CVE-2020-13700 is a high-severity Authorization Bypass Through User-Controlled Key vulnerability in the ACF to REST API WordPress plugin, affecting versions <= 3.2.0. 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 3.3.0; sites on affected versions should update now. Disclosed May 2020, reported by Mariusz Poplawski.
Vulnerability Overview
An issue was discovered in the acf-to-rest-api plugin through 3.1.0 for WordPress. It allows an insecure direct object reference via permalinks manipulation, as demonstrated by a wp-json/acf/v3/options/ request that reads sensitive information in the wp_options table, such as the login and pass values. Issue was finally patched in 3.3.0
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-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in ACF to REST API <= 3.2.0 takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For ACF to REST API the fix is 3.3.0: builds <= 3.2.0 are affected, anything from 3.3.0 onward is not.
Remediation
Update to version 3.3.0, 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: ACF to REST API 3.3.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in ACF to REST API
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C