ACF Quick Edit Fields <= 3.2.2 - Authenticated (Contributor+) Insecure Direct Object Reference
Strategic Overview
- Status
- Patched in 3.2.3
- Affected Plugin
- ACF Quick Edit Fields
- Affected Version
<= 3.2.2- CVSS
- 6.5Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2023-7286
At a glance
CVE-2023-7286 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the ACF Quick Edit Fields WordPress plugin, affecting versions <= 3.2.2. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.2.3; sites on affected versions should update now. Disclosed December 2022, reported by Chris Grello.
Vulnerability Overview
The plugin ACF Quick Edit Fields for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 3.2.2. This makes it possible for attackers without the edit_users capability to access metadata of other users, this includes contributor-level users and above.
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 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 Quick Edit Fields <= 3.2.2 takes an account at Contributor level or above. 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 Quick Edit Fields the fix is 3.2.3: builds <= 3.2.2 are affected, anything from 3.2.3 onward is not.
Remediation
Update to version 3.2.3, 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 Quick Edit Fields 3.2.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C