CVE-2026-97195: Secure Custom Fields (WordPress plugin) · Cross-site Scripting
Affects Secure Custom Fields (WordPress plugin)Source CVE Database V5
Not known to be exploited : upgrade to 6.9.8 soon.
Data as of 8 Nov 2026, 07:03 UTC
Rated High 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 is fixed. No other mitigation is required as the official fix addresses the issue.
Description
A Cross-site Scripting (XSS) vulnerability exists in the Secure Custom Fields WordPress plugin before version 6.9.8. The flaw arises because the plugin does not sanitize a persisted field definition before using it as an HTML attribute name. This allows a user with the ability to configure fields to inject JavaScript payloads that execute in the browsers of users viewing the affected fields. In multisite environments, site administrators without the unfiltered_html capability can exploit this to inject scripts into other users' sessions.