Not rated
CVE-2026-97195 Secure Custom Fields < 6.9.8 - Admin+ Stored XSS via HTML Attribute Name Injection into Field Definition
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.
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| Secure Custom Fields 6.9 | earliest → < 6.9.8 | 6.9.8 |
Other CVEs of Secure Custom Fields
The 6 CVEs of Secure Custom Fields →
CVE-2026-97194
Secure Custom Fields < 6.9.8 - Contributor+ Unpublished Post Title and Status Disclosure via Relational Fields
Not rated
CVE-2026-97193
Secure Custom Fields < 6.9.8 - Contributor+ Relationship Field Update on Arbitrary Objects via IDOR
Not rated
CVE-2026-97192
Secure Custom Fields < 6.9.8 - Contributor+ Admin-Restricted Custom Field Update via Post Save Path
Not rated
CVE-2026-92403
The Secure Custom Fields WordPress plugin before 6.9.4 does not properly verify that a front-end form submission…
3.7
Low