Skip to content
Fencer Vulns
low 2.7

CVE-2026-97191 json

Advanced Custom Fields < 6.8.11 - Contributor+ Admin-Restricted Custom Field Update via Post Save Path

published 2026-11-07 2 d ago modified 2026-11-07 38 h ago also EUVD-2026-118957

cvss
2.7
version 3.1, CISA ADP
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 6%
public exploits
0
none known

Summary

The Advanced Custom Fields (ACF®) WordPress plugin before 6.8.11 does not re-apply its field-group location rules when persisting values submitted through the post editor save path, allowing users with contributor-level access and above to write custom fields the site restricted to administrators onto their own posts.

Patch / fix

  • Unknown Advanced Custom Fields (ACF®) 6.8.11

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
38 h ago

Exploit prediction

0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • wpscan.com https://wpscan.com/vulnerability/3eb847d4-6649-4f71-8dc7-e739a6317409/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 2.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N

Affected products

  • Unknown Advanced Custom Fields (ACF®)

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.