CVE-2026-97194: Secure Custom Fields (WordPress plugin) · Information Exposure
Affects Secure Custom Fields (WordPress plugin)Source CVE Database V5
Not known to be exploited : upgrade to 6.9.8 when convenient.
Data as of 8 Nov 2026, 07:03 UTC
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.9.8
Exploitation evidence
Disclosed: evidence found.
CVE published 8 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 7 Nov 2026.
What to do
Upgrade Secure Custom Fields (WordPress plugin) to 6.9.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Secure Custom Fields | Affected
| Fixed in
|
AI-suggested
Upgrade the Secure Custom Fields plugin to version 6.9.8 or later, where this vulnerability has been fixed. No additional mitigation steps are required once the plugin is updated.
Description
A vulnerability in the Secure Custom Fields WordPress plugin before version 6.9.8 allows users with post-editing permissions (Contributor and above) to access titles and non-public statuses of unpublished posts belonging to other users. This occurs because the plugin does not perform proper read-permission checks when rendering relational field values.