# CVE-2026-120491: Wing FTP Server before 8.2.6 Stored XSS via nowpath in Legacy Activity Page


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** GHSA-76h6-gfhv-jpgq

## What is CVE-2026-120491?

CVE-2026-120491 is a medium-severity vulnerability in Wing FTP Server, published on 2 Nov 2026. 

### Official description

Wing FTP Server before 8.2.6 contains a stored cross-site scripting vulnerability that allows authenticated web-client users to inject script by sending a crafted nowpath parameter to webclient/makethumb.html. Attackers can break out of the directory CDATA section in admin_get_lastconn.html XML to forge a connection id, which executes in administrators' browsers when admin_connection_list.html auto-refreshes, enabling Lua console abuse.

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

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


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

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

## Is CVE-2026-120491 being exploited?

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

Public exploit code:

- Python PoC for my first CVE (github_poc): https://github.com/3jee/CVE-2026-120491

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120491 is a medium-severity vulnerability in Wing FTP Server, published on 2 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120491 in the wild and no public exploit code.

Affected product: Wing FTP Server. 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-120491/ (Markdown: https://insights.sbomify.com/CVE-2026-120491/index.md)
```

## Sources

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

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