CVE-2026-97195lowCWE-79

CVE-2026-97195: low-severity vulnerability in Secure Custom Fields

Secure Custom Fields < 6.9.8 - Admin+ Stored XSS via HTML Attribute Name Injection into Field Definition

Published

Follow this CVE+ Monitor Secure Custom Fields

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

28Vexday Risk Score

No sign of exploitation. It has a public proof of concept.

ssvc Attendcvss 3.5epss 0.1%
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.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N
Affected products
Unknown · Secure Custom Fields
⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
Related CVEs — Secure Custom Fields

In the same product, most dangerous first.

CVE-2024-9529MEDIUMSecure Custom Fields < 6.3.6.3 - Admin+ Remote Code ExecutionEPSS 0.4%CVE-2026-92403LOWSecure Custom Fields < 6.9.4 - Unauthenticated Post Modification via Front-End Form ID SubstitutionEPSS 0.3%CVE-2026-97194LOWSecure Custom Fields < 6.9.8 - Contributor+ Unpublished Post Title and Status Disclosure via Relational FieldsEPSS 0.2%CVE-2026-97193LOWSecure Custom Fields < 6.9.8 - Contributor+ Relationship Field Update on Arbitrary Objects via IDOREPSS 0.2%CVE-2026-97192LOWSecure Custom Fields < 6.9.8 - Contributor+ Admin-Restricted Custom Field Update via Post Save PathEPSS 0.2%