Skip to main content
CVE-2026-97195VulnerabilityPublished

The Secure Custom Fields WordPress plugin before 6.9.8 does not sanitize a persisted field definition before emitting

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-97195· High

Not known to be exploited : upgrade to 6.9.8 soon.

Data as of 8 Nov 2026, 08:05 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 6.9.8

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Upgrade Secure Custom Fields (WordPress plugin) to 6.9.8.

Affected software

ProductAffectedFixed in
Secure Custom FieldsAffected
  • <6.9.8
Fixed in
  • 6.9.8

AI-suggested

A fix is available in Secure Custom Fields version 6.9.8. Users should update to version 6.9.8 or later to remediate this vulnerability.

Description

The Secure Custom Fields WordPress plugin versions before 6.9.8 contain a vulnerability where a persisted field definition is not sanitized before being emitted as an HTML attribute name. This allows a user with the ability to configure fields to store a payload that executes JavaScript in the browsers of users viewing the affected field. In multisite environments, this can enable a site administrator without the unfiltered_html capability to inject script into other users' sessions.

References

Community reviews

Loading reviews…