Quick answers
- Is CVE-2026-110813 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110813 being exploited in the wild.
- How severe is CVE-2026-110813?
- Informational severity, published 6 November 2026.
- Which products and versions are affected?
- Advanced Custom Fields before 6.8.11.
- Is there a fix for CVE-2026-110813?
- Yes: fixed in 6.8.11. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-110813 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-110813?
- Check whether you run Advanced Custom Fields at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 6.8.11
Technical details
The plugin fails to properly sanitize stored field definitions that can be modified through its comment handling mechanism, allowing unauthenticated users to inject a payload that becomes an HTML attribute name and executes as JavaScript. The vulnerability is a stored XSS (CWE-79) exploitable via network access without authentication, affecting any visitor or administrator who views a page rendering the compromised field.
Affected products
- Advanced Custom Fields Advanced Custom Fields before 6.8.11
Timeline
- 2026-11-04: disclosed
- 2026-11-06: advisory