Advanced Custom Fields <= 6.0.2 - Authenticated (Contributor+) Information Disclosure
Strategic Overview
- Status
- Patched in 6.0.3
- Affected Plugin
- Advanced Custom Fields (ACF®)
- Affected Version
<= 6.0.2- CVSS
- 4.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2022-40696
At a glance
CVE-2022-40696 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Advanced Custom Fields (ACF®) WordPress plugin, affecting versions <= 6.0.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 6.0.3; sites on affected versions should update now. Disclosed October 2022, reported by Juan Hoffmann.
Vulnerability Overview
The Advanced Custom Fields plugin for WordPress is vulnerable to Sensitive Data Exposure in versions up to, and including, 6.0.2. While the ACF shortcode ensures that the ACF data being accessed is valid data that has been entered into ACF fields, it may be possible with certain site configurations, that contributor-level users may 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 interaction from a victim user.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in Advanced Custom Fields (ACF®) <= 6.0.2 takes an account at Contributor level or above. 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 Advanced Custom Fields (ACF®) the fix is 6.0.3: builds <= 6.0.2 are affected, anything from 6.0.3 onward is not.
Remediation
Update to version 6.0.3, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: Advanced Custom Fields (ACF®) 6.0.3 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Advanced Custom Fields (ACF®)
- 8.8CVE-2023-1196: Advanced Custom Fields <= 6.0.7 PHP Object Injection
CVE-2023-1196 - 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 - 6.5CVE-2021-20866: Advanced Custom Fields <= 5.10 Information Disclosure
CVE-2021-20866 - 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-2020-36172: Advanced Custom Fields <= 5.8.11 Cross-Site Scripting
CVE-2020-36172 - 5.5CVE-2024-45429: Advanced Custom Fields <= 6.3.5 Stored XSS
CVE-2024-45429
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C