Advanced Custom Fields <= 5.10 - Missing Authorization to Information Disclosure
Strategic Overview
- Status
- Patched in 5.11
- Affected Plugin
- Advanced Custom Fields Pro
- Affected Version
< 5.11- CVSS
- 6.5Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2021-20866
At a glance
CVE-2021-20866 is a medium-severity Missing Authorization vulnerability in the Advanced Custom Fields Pro WordPress plugin, affecting versions < 5.11. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 5.11; sites on affected versions should update now. Disclosed December 2021, reported by Keitaro Yamazaki.
Vulnerability Overview
Advanced Custom Fields versions prior to 5.11 and Advanced Custom Fields Pro versions prior to 5.11 contain a missing authorization vulnerability in obtaining the user list which may allow a user to obtain the unauthorized information via unspecified vectors.
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-862: Missing Authorization
Reaching this weakness in Advanced Custom Fields Pro < 5.11 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Advanced Custom Fields Pro the fix is 5.11: builds < 5.11 are affected, anything from 5.11 onward is not.
Remediation
Update to version 5.11, 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: Advanced Custom Fields Pro 5.11 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 7.5CVE-2021-20865: Advanced Custom Fields <= 5.10 Information Disclosure
CVE-2021-20865 - 6.5CVE-2022-23183: Advanced Custom Fields <= 5.12 Information Disclosure
CVE-2022-23183 - 5.4CVE-2024-37250: Advanced Custom Fields Pro Missing Authorization
CVE-2024-37250 - 5.4CVE-2024-37250: Advanced Custom Fields Pro Missing Authorization
CVE-2024-37250
Other vulnerabilities in Advanced Custom Fields Pro
- 9.9CVE-2024-34761: Advanced Custom Fields Pro <= 6.2.9 Code Injection
CVE-2024-34761 - 8.8CVE-2024-34762: Advanced Custom Fields Pro <= 6.2.9 LFI
CVE-2024-34762 - 6.4CVE-2023-6701: Advanced Custom Fields <= 6.2.4 Stored XSS
CVE-2023-6701 - 6.1CVE-2023-30777: Advanced Custom Fields 5.8.10… Reflected XSS
CVE-2023-30777 - 6.1CVE-2021-24241: Advanced Custom Fields Pro <= 5.9.0 Reflected XSS
CVE-2021-24241 - 5.5CVE-2024-45429: Advanced Custom Fields <= 6.3.5 Stored XSS
CVE-2024-45429 - 5.1CVE-2024-9529: Advanced Custom Fields Limited Arbitrary Function Call
CVE-2024-9529 - 4.4CVE-2024-49593: Advanced Custom Fields & Secure Custom Fields <=
CVE-2024-49593
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C