Read the docs

Stored cross-site scripting in Secure Custom Fields plugin

Priority LOW 16CWE-79Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
Required
Attack complexity
Low
Impact type
Cross-site scripting
Confidentiality · integrity · availability
Low · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-79.

Summary

The Secure Custom Fields WordPress plugin before 6.9.8 does not sanitize a stored field definition before printing part of it as an HTML attribute name (CWE-79). A user who can configure fields stores a payload that runs as JavaScript in the browser of any user viewing a page with that field, and on multisite it reaches other users' sessions. A public exploit is linked in the references.

Written with Claude Haiku 5.5 from the sources below · 2026-11-08

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00142 3rd percentileScored 2026-11-16
Public exploit Yes 1 exploit referenceTagged by the CNA
Fix Fixed Secure Custom Fields (Unknown): 6.9.8

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
UnknownSecure Custom Fieldsbefore 6.9.86.9.8Patch availableCNA
  • Secure Custom Fields VendorUnknown Affected before 6.9.8 Fixed in 6.9.8 Patch available CNA

Remediation

Update Secure Custom Fields to version 6.9.8 or later, which fixes the flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-11-08

  • Fix · CNA Secure Custom Fields (Unknown) Fixed in 6.9.8

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Secure Custom Fields 6.9.8

    4 records Highest priority Priority LOW 4 LOW

    Other records, highest priority first

    • TI-2026-86766 Secure Custom Fields leaks unpublished post titles and statusesPriority LOW 13
    • TI-2026-86765 Secure Custom Fields lets contributors modify arbitrary objectsPriority LOW 13
    • TI-2026-86764 Improper access control in Secure Custom Fields WordPress pluginPriority LOW 13

Timeline

  1. 2026-11-08 Threatist record created from CVE-2026-97195
  2. 2026-11-08 Alias added: GHSA-47pm-jg2m-gx97
  3. 2026-11-08 CVSS score added · CISA ADP
  4. 2026-11-08 Weakness changed · CISA ADP
  5. 2026-11-08 CISA SSVC decision points changed

References

Sources