Skip to main content
CVE-2026-97190VulnerabilityPublished

The Advanced Custom Fields (ACF®) WordPress plugin before 6.8.11 does not verify that a user is allowed to edit the

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-97190· High

Not known to be exploited : upgrade to 6.8.11 soon.

Data as of 7 Nov 2026, 07:36 UTC

Severity
High

Rated High 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

  1. Disclosed: evidence found.

    CVE published 7 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Advanced Custom Fields (ACF®)Affected
  • >=6.2.0 <6.8.11
Fixed in
  • 6.8.11

AI-suggested

Upgrade the Advanced Custom Fields (ACF®) WordPress plugin to version 6.8.11 or later, where this authorization check issue has been fixed. No other mitigation steps are indicated as the fix is available in the updated version.

Description

The Advanced Custom Fields (ACF®) WordPress plugin versions before 6.8.11 contain a vulnerability where the plugin does not verify user permissions before modifying bidirectional relationship fields. This allows users with contributor-level access or higher to add or remove references to their own objects on posts, users, or terms they cannot normally edit.

References

Community reviews

Loading reviews…