Quick answers
- Is CVE-2026-97189 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-97189 being exploited in the wild.
- How severe is CVE-2026-97189?
- Informational severity, published 7 November 2026.
- Which products and versions are affected?
- Advanced Custom Fields before 6.8.11.
- Is there a fix for CVE-2026-97189?
- 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-97189 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-97189?
- 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 does not perform read-permission checks when rendering and formatting relational field values, allowing authenticated users with post-editing access (Contributor role and above) to disclose titles and non-public statuses of unpublished posts. This is a missing authorization check (CWE-200) that requires the attacker to have at least Contributor access to a WordPress installation. The vulnerability has been fixed in version 6.8.11.
Affected products
- Advanced Custom Fields Advanced Custom Fields before 6.8.11
Timeline
- 2026-11-04: disclosed
- 2026-11-07: advisory