CVE-2026-97195
Secure Custom Fields < 6.9.8 - Admin+ Stored XSS via HTML Attribute Name Injection into Field Definition
- Low 3.5
- A public exploit reference is listed
Description
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.
Key facts
- Published
- 8 Nov 2026
- Last changed
- 8 Nov 2026
- Assigned by
- WPScan
- EPSS
- 0.142% likely to be exploited in the next 30 days, higher than 3.621% of CVEs (scores for 15 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: no; Technical impact: partial
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 3.5CVSS 3.1, Lowfrom CISA (ADP container)
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Unknown | Secure Custom Fields |
|
Timeline
- 8 Nov 2026 Published
Weakness
Practice this bug class
HackZoneLabs has a hands-on lab on XSS (stored, reflected, DOM) (CWE-79).