# CVE-2026-97336: CMB2 <= 2.13.0 - Unauthenticated Stored Cross-Site Scripting via 'file_list' Field Type

> Unauthenticated attackers can inject scripts via file_list fields in CMB2, requiring specific theme or plugin configurations to exploit.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-c4g5-wq6m-xp45

## What is CVE-2026-97336?

CVE-2026-97336 is a high-severity cross-site scripting vulnerability in jtsternberg CMB2, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The CMB2 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'file_list' Field Type in all versions up to, and including, 2.13.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is only exploitable when an integrating plugin or theme registers a file_list field on a publicly accessible front-end form or a user meta box, as CMB2 is a developer library and does not expose these fields by default.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

No fix has been published for CVE-2026-97336 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-97336 being exploited?

There is no known exploitation of CVE-2026-97336 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97336 and fix it if it is affected.

What it is: CVE-2026-97336 is a high-severity cross-site scripting vulnerability in jtsternberg CMB2, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-97336 in the wild and no public exploit code.

Affected product: jtsternberg CMB2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-97336/ (Markdown: https://insights.sbomify.com/CVE-2026-97336/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97336
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97336
- OSV: https://osv.dev/vulnerability/CVE-2026-97336

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97336/
Summaries are generated and may contain mistakes; the official description above is the record.