CVE-2026-97195 Secure Custom Fields < 6.9.8 - Admin+ Stored XSS via HTML Attribute Name Injection into Field Definition
LowCVSS 3.5
EPSS 0.19%
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: no · technical impact: partial
- Technology
- WordPress
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.
Upgrade path
1 package: 1 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| wordpress secure-custom-fields(WordPress) | < 6.9.8 | 6.9.8 | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| wordpress secure-custom-fields(WordPress) | < 6.9.8 | 6.9.8 |
References
- wpscan.com exploit technical-description vdb-entry
- Wordfence Intelligence third-party-advisory
- www.cve.org
- ENISA EUVD EUVD-2026-119464 third-party-advisory