Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.newCreate a CVE report
Check your stack
CVE-2026-97195

Secure Custom Fields < 6.9.8 - Admin+ Stored XSS via HTML Attribute Name Injection into Field Definition

Products / packages Unknown Secure Custom Fields

Published

Share

Severity and exploitation

Not in CISA KEV

KEV coverage does not rule out exploitation.

KEV checked 14/11/2026, 21:55:35 UTC
CISA-ADP · CVSS:3.1 · 3.5
Assessment vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N

Severity

low3.5

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Exploit reference published

Source-linked evidence; not proof of attacks in the wild or independent validation.

Remediation

Fix status not established

No structured fix or guidance is available here. Check the latest publisher advisory.

What this means

The Secure Custom Fields WordPress plugin before 6.9.8 has a stored XSS vulnerability, allowing an admin to inject JavaScript into field definitions, which executes in users' browsers. An attacker with field configuration access can store a malicious payload. The impact is cross-site scripting.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

Unknown · WPScan

Secure Custom Fields

1 range
WPScan version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

0 → before 6.9.8

semver versions

unaffected

unknown

Other versions: unaffected

Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

No structured fix or remediation guidance is available here. Check the full source description and vendor’s latest advisory for a patch or workaround; do not assume another version is safe.

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

The sources identify public exploit references. We have not independently tested them; their availability does not establish exploitation in the wild.

wpscan.com/vulnerability/a2fb296c-e7f4-4a40-b503-aa709c7b88bb/ ↗Attributed to WPScan

Original source description

Read the full publisher 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.

References

1 sources
wpscan.com/vulnerability/a2fb296c-e7f4-4a40-b503-aa709c7b88bb/
Public exploit referenceWPScan

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-97195

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-79 ↗

CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

CISA-ADP

Related →
Contributing organizations · 2
WPScan

Assigning organization

2026-11-08
CISA-ADP

Additional data publisher

2026-11-08

Timeline

All times UTC

  1. Advisory published

    Publication date supplied by the source.

  2. Source updated

    Latest modification date supplied by the source.

  3. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
  1. CVE · CVE-2026-97195

    Observed 2026-11-08T19:23:37.881Z · upstream updated 2026-11-08T19:05:28.489Z

    Severity assessment changed

    before

    []

    after

    [
  {
    "source": "CISA-ADP",
    "vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N",
    "score": 3.5
  }
]
    Weakness classification changed

    before

    []

    after

    [
  {
    "id": "CWE-79",
    "description": "CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')",
    "source": "CISA-ADP"
  }
]
    Prioritization updated

    before

    []

    after

    [
  {
    "source": "CISA-ADP",
    "type": "SSVC",
    "role": "CISA Coordinator",
    "timestamp": "2026-11-08T18:58:43.919986Z",
    "decisions": [
      {
        "name": "Exploitation",
        "value": "none"
      },
      {
        "name": "Automatable",
        "value": "no"
      },
      {
        "name": "Technical Impact",
        "value": "partial"
      }
    ]
  }
]

Large field values are marked as truncated previews. Original source snapshots remain retained.

Showing up to 50 most recent observed changes.