XSS in Secure Custom Fields
CVE-2026-97195
The Secure Custom Fields WordPress plugin before 6.9.8 does not sanitize a persisted field definition before emitting part of it as an HTML attribute name, allowing a user able to configure its fields to store a payload that executes as JavaScript in the browser of any user who views a page rendering the affected field, which on multisite lets a site administrator who lacks the unfiltered_html capability inject script into other users' sessions.
Vulnerability class: XSS (Cross-Site Scripting)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 3.5 (Low). Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
- Secure Custom Fields
Weakness classification (CWE)
References
- wpscan.com/vulnerability/a2fb296c-e7f4-4a40-b503-aa709c7b88bb/ (technical-description, exploit, vdb-entry)
Frequently asked questions
- What is CVE-2026-97195?
- CVE-2026-97195 is a low-severity vulnerability in Secure Custom Fields, classified under Cross-site Scripting. CVSS score: 3.5/10. Published 2026-11-08.
- How severe is CVE-2026-97195?
- Low severity. CVSS v3 base score is 3.5 out of 10.