The Advanced Custom Fields (ACF®) WordPress plugin before 6.8.11 does not re-apply its field-group location rules when
Source GCVE Database
Not known to be exploited : upgrade to 6.8.11 when convenient.
Data as of 7 Nov 2026, 07:37 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 6.8.11
Exploitation evidence
Disclosed: evidence found.
CVE published 7 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade Advanced Custom Fields (ACF®) (WordPress plugin) to 6.8.11.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Advanced Custom Fields (ACF®) | Affected
| Fixed in
|
AI-suggested
Upgrade the Advanced Custom Fields (ACF®) WordPress plugin to version 6.8.11 or later, where this issue is fixed. No other mitigation is indicated in the available data.
Description
The Advanced Custom Fields (ACF®) WordPress plugin versions before 6.8.11 have a vulnerability where field-group location rules are not re-applied when saving values through the post editor. This allows users with contributor-level access and above to write custom fields that are normally restricted to administrators onto their own posts.