# CVE-2026-64950: Stored Cross-Site Scripting via Directory Name in File Manager Create Directory

> Stored XSS in Pandora FMS File Manager allows attackers to execute scripts via directory names, potentially leading to session hijacking or code execution.

- **Severity:** High 8.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/S:N/AU:Y/R:U/V:C/RE:L/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-wqwc-mc6v-2fqc

## What is CVE-2026-64950?

CVE-2026-64950 is a high-severity cross-site scripting vulnerability in Pandora FMS, published on 1 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Missing input validation and output encoding on the directory name parameter in File Manager's Create Directory allows stored XSS, executing without user interaction. Affects Pandora FMS from 777 onwards.

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

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


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

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

## Is CVE-2026-64950 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64950 is a high-severity cross-site scripting vulnerability in Pandora FMS, published on 1 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-64950 in the wild and no public exploit code.

Affected product: Pandora FMS. 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-64950/ (Markdown: https://insights.sbomify.com/CVE-2026-64950/index.md)
```

## Sources

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

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