CVE-2022-40696 is a low severity (CVSS 3.7) sensitive information exposure in the Advanced Custom Fields (ACF) WordPress plugin, versions 3.1.1 through 6.0.2. Anyone can reach it without logging in. Update to ACF 6.0.3 or later. Check your installed version and apply the update through your normal change process.
What's affected
The record lists Advanced Custom Fields (ACF) from WP Engine, from version 3.1.1 through 6.0.2. Patchstack gives the patched version as 6.0.3. Patchstack gives the required privilege as none, so it is unauthenticated.
The record scores it 3.7 (Low) with vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N. The weakness class is CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor). Versions before 3.1.1 are not covered by this record.
How to check if you're exposed
Start with an inventory. If you manage the site with WP-CLI, this lists every plugin with its version and whether an update is waiting:
wp plugin list --fields=name,status,version,update
Look for the folder advanced-custom-fields. That folder name comes from the Patchstack entry for this issue, so confirm it matches what sits under wp-content on your site. Without WP-CLI, open the Plugins screen in the dashboard and read the version shown under the name. Version 6.0.2 or lower is affected. Version 6.0.3 or later is patched.
Check staging copies, old multisite subsites and inactive plugins too. A deactivated plugin is still on disk, and some of these bugs are reachable through files that load even when the plugin is switched off, so deactivation alone is not a fix. Delete what you do not use.
What to do now
- Update Advanced Custom Fields (ACF) to 6.0.3 or a newer release.
- Review the site's user list and remove accounts you do not recognise.
- Turn on automatic updates for the plugin so the next fix lands without a ticket.
Why it matters
The record puts this in the sensitive information exposure class: some piece of data reaches someone who should not see it. The score is low because the vector requires high attack complexity and the confidentiality impact is limited. Patchstack classes it as sensitive data exposure and rates its own priority Low.
I could not find in the sources I read what information leaks, so I will not name it. The affected range is broad, from 3.1.1, which covers years of releases, and ACF is installed on a very large number of sites, so even a low severity issue touches a lot of installs. That makes it a routine update, not an emergency, and a good test of whether your plugin update process works. The record's KEV flag is false, and nothing I fetched reports exploitation in the wild.
Quick check
Why bother with a low severity issue?
Because the fix is a normal plugin update and ACF is widely deployed. Small leaks help attackers build a picture of a site before they try something bigger.
Which versions are affected?
The record says 3.1.1 through 6.0.2. Patchstack lists 6.0.3 as patched.
Sources
Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.
Last reviewed: 19 October 2026.