CVE-2022-40696

Advanced Custom Fields <= 6.0.2 - Authenticated (Contributor+) Information Disclosure

2022-10-18 00:00
Juan Hoffmann

Strategic Overview

Status
Patched in 6.0.3
Affected Version
<= 6.0.2
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2022-40696
View all Advanced Custom Fields (ACF®) vulnerabilities

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

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C