CVE-2026-97195: 
WordPress vulnerability analysis and mitigation

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.


Source: NVD

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-97195LOW3.5
  • secure-custom-fields
NoYesNov 08, 2026
CVE-2026-97194LOW2.7
  • secure-custom-fields
NoYesNov 08, 2026
CVE-2026-97193LOW2.7
  • secure-custom-fields
NoYesNov 08, 2026
CVE-2026-97192LOW2.7
  • secure-custom-fields
NoYesNov 08, 2026
CVE-2026-96963LOW2.7
  • pie-register
NoYesNov 08, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management