# CVE-2024-8404: Arbitrary File Deletion in PaperCut NG/MF Web Print Hot folder

> An attacker with local low-privilege access can delete arbitrary files on Windows servers running PaperCut with Web Print enabled.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2024
- **Updated:** 13 May 2025
- **Also known as:** GHSA-9cxr-86mw-8jw2

## What is CVE-2024-8404?

CVE-2024-8404 is a high-severity path traversal vulnerability in PaperCut NG, PaperCut MF, published on 26 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An arbitrary file deletion vulnerability exists in PaperCut NG/MF, specifically affecting Windows servers with Web Print enabled. To exploit this vulnerability, an attacker must first obtain local login access to the Windows Server hosting PaperCut NG/MF and be capable of executing low-privilege code directly on the server via the web-print-hot-folder. 

Important: In most installations, this risk is mitigated by the default Windows Server configuration, which restricts local login access to Administrators only. However, this vulnerability could pose a risk to customers who allow non-administrative users to log into the local console of the Windows environment hosting the PaperCut NG/MF application server.

Update:

This CVE has been updated in May 2025 to update the fixed version and fix process. Please refer to the May 2025 Security Bulletin.

Note: 

This CVE has been split from CVE-2024-3037.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2024-8404?

It affects 2 products.


Products: Papercut Papercut Mf, Papercut Papercut Ng.

## How do I fix CVE-2024-8404?

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

## Is CVE-2024-8404 being exploited?

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

## Other vulnerabilities in PaperCut NG, PaperCut MF

- [CVE-2023-27350](https://insights.sbomify.com/CVE-2023-27350/): PaperCut MF/NG Improper Access Control (critical 9.8, exploited in the wild)
- [CVE-2026-82078](https://insights.sbomify.com/CVE-2026-82078/): PaperCut NG/MF Unsafe Reflection (critical 9.4, exploited in the wild)
- [CVE-2026-81578](https://insights.sbomify.com/CVE-2026-81578/): PaperCut NG/MF Missing Authentication for Critical Function (high 8.8, exploited in the wild)
- [CVE-2023-2533](https://insights.sbomify.com/CVE-2023-2533/): PaperCut NG/MF Cross-Site Request Forgery (CSRF) (high 8.4, exploited in the wild)
- [CVE-2023-27351](https://insights.sbomify.com/CVE-2023-27351/): PaperCut NG/MF Improper Authentication (high 8.2, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8404 and fix it if it is affected.

What it is: CVE-2024-8404 is a high-severity path traversal vulnerability in PaperCut NG, PaperCut MF, published on 26 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8404 in the wild and no public exploit code.

Affected product: PaperCut NG, PaperCut MF. 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-2024-8404/ (Markdown: https://insights.sbomify.com/CVE-2024-8404/index.md)
```

## Sources

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

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