# CVE-2026-30578: Cross-site scripting in n/a

> A malicious user can execute arbitrary JavaScript via the dir parameter in File Thinghie, potentially compromising user sessions.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Mar 2026
- **Updated:** 23 Mar 2026
- **Also known as:** GHSA-pqvq-hmh6-qwqj

## What is CVE-2026-30578?

CVE-2026-30578 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

File Thinghie 2.5.7 is vulnerable to Cross Site Scripting (XSS). A malicious user can leverage the "dir" parameter of the GET request to invoke arbitrary javascript code.

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

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

It affects 1 product.


Products: Leefish File Thingie.

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

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

## Is CVE-2026-30578 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-53942](https://insights.sbomify.com/CVE-2023-53942/): File Thingie 2.5.7 Authenticated Arbitrary File Upload Remote Code Execution (critical 9.4)
- [CVE-2019-25471](https://insights.sbomify.com/CVE-2019-25471/): FileThingie 2.5.7 Arbitrary File Upload via ft2.php (critical 9.3)
- [CVE-2026-30579](https://insights.sbomify.com/CVE-2026-30579/): Cross-site scripting in n/a (medium 6.5)
- [CVE-2026-30580](https://insights.sbomify.com/CVE-2026-30580/): Path traversal in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-30578 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-30578 in the wild and no public exploit code.

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

## Sources

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

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