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.
History

Sun, 08 Nov 2026 08:00:00 +0000

Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions secure Custom Fields
Vendors & Products Wordpress-extensions
Wordpress-extensions secure Custom Fields

Sun, 08 Nov 2026 07:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-79

Sun, 08 Nov 2026 06:15:00 +0000

Type Values Removed Values Added
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.
Title Secure Custom Fields < 6.9.8 - Admin+ Stored XSS via HTML Attribute Name Injection into Field Definition
References

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published: 2026-11-08T06:00:28.542Z

Updated: 2026-11-08T06:00:28.542Z

Reserved: 2026-09-24T08:43:31.127Z

Link: CVE-2026-97195

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-08T06:17:06.350

Modified: 2026-11-08T06:17:06.350

Link: CVE-2026-97195

cve-icon Redhat

No data.