Skip to main content
CVE-2026-110813VulnerabilityPublished

The Advanced Custom Fields (ACF®) WordPress plugin before 6.8.11 does not properly sanitize a stored field definition

Source GCVE Database

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

Not known to be exploited : upgrade to 6.8.11 soon.

Data as of 6 Nov 2026, 07:33 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 6 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 5 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.8.11
Fixed in
  • 6.8.11

AI-suggested

A fix is available in version 6.8.11 of the Advanced Custom Fields plugin. Users should upgrade to version 6.8.11 or later to remediate this vulnerability. No other mitigation or temporary workaround is indicated.

Description

The Advanced Custom Fields (ACF®) WordPress plugin versions before 6.8.11 contain a vulnerability where a stored field definition is not properly sanitized. This flaw allows unauthenticated users to inject malicious payloads via comment handling, which are then emitted as HTML attribute names and executed as JavaScript in the browsers of visitors or administrators viewing the affected field.

References

Community reviews

Loading reviews…