# CVE-2026-30580: Path traversal in n/a

> A malicious user can read arbitrary files on the target system via the create folder from URL feature in File Thingie.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2026
- **Updated:** 23 Mar 2026
- **Also known as:** GHSA-293m-mfcv-f7g4

## What is CVE-2026-30580?

CVE-2026-30580 is a medium-severity path traversal vulnerability in n/a, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

File Thingie 2.5.7 is vulnerable to Directory Traversal. A malicious user can leverage the "create folder from url" functionality of the application to read arbitrary files on the target system.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Leefish File Thingie.

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

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

## Is CVE-2026-30580 being exploited?

There is no known exploitation of CVE-2026-30580 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-30578](https://insights.sbomify.com/CVE-2026-30578/): Cross-site scripting in n/a (medium 6.5)
- [CVE-2026-30579](https://insights.sbomify.com/CVE-2026-30579/): Cross-site scripting in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-30580 is a medium-severity path traversal vulnerability in n/a, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-30580 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-30580/ (Markdown: https://insights.sbomify.com/CVE-2026-30580/index.md)
```

## Sources

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

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