# CVE-2026-107594: File Upload to Order < 1.1.4 - Unauthenticated Arbitrary File Deletion

> Unauthenticated attackers can delete arbitrary files via path traversal in the File Upload to Order plugin, potentially leading to full site compromise.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-7x7h-q4vm-3v3h

## What is CVE-2026-107594?

CVE-2026-107594 is a critical path traversal vulnerability in Unknown File Upload to Order, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The File Upload to Order WordPress plugin before 1.1.4 does not validate or confine a file path taken from attacker-controlled session data before deleting the file, and the action that performs the deletion is reachable by unauthenticated users, allowing them to delete arbitrary files on the server, including files whose removal leads to full site compromise.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2026-107594 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107594 is a critical path traversal vulnerability in Unknown File Upload to Order, published on 14 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-107594 in the wild and no public exploit code.

Affected product: Unknown File Upload to Order. 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-107594/ (Markdown: https://insights.sbomify.com/CVE-2026-107594/index.md)
```

## Sources

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

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