CVE-2026-97189VulnerabilityPublished 7 Nov 2026

The Advanced Custom Fields (ACF®) WordPress plugin before 6.8.11 does not perform a read-permission check when it

Source GCVE Database

Compare

Authoritative record:CVE-2026-97189· Medium

Not known to be exploited : upgrade to 6.8.11 when convenient.

Data as of 7 Nov 2026, 07:37 UTC

Severity

Medium

Rated Medium 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

Disclosed: evidence found.
CVE published 7 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-3r78-26qx-3q7m

What to do

Upgrade Advanced Custom Fields (ACF®) (WordPress plugin) to 6.8.11.

Affected software

Product	Affected	Fixed in
Advanced Custom Fields (ACF®)	Affected <6.8.11	Fixed in 6.8.11

AI-suggested

Upgrade the Advanced Custom Fields (ACF®) WordPress plugin to version 6.8.11 or later, where this read-permission check issue has been addressed. No other mitigation steps are indicated.

Description

The Advanced Custom Fields (ACF®) WordPress plugin versions prior to 6.8.11 lack a read-permission check when rendering and formatting relational field values. This flaw allows users with post-editing capabilities (Contributor role and above) to view titles and non-public statuses of unpublished posts owned by other users.

Impact

Users with post-editing permissions can disclose titles and non-public statuses of other users' unpublished posts. This may lead to unintended information leakage within the WordPress environment, potentially exposing sensitive editorial content or unpublished work to unauthorized users with contributor-level access or higher.

Summary

A vulnerability in the Advanced Custom Fields (ACF®) WordPress plugin before version 6.8.11 causes it to omit a read-permission check during the rendering and formatting of relational field values. As a result, users with the ability to edit posts, such as those with Contributor roles or higher, can access sensitive information including titles and unpublished status of posts they do not own. This information disclosure issue arises from insufficient access control enforcement within the plugin's handling of relational fields.

References

Community reviews

Loading reviews…