# CVE-2022-3899: 3DPrint < 3.5.6.9 - Arbitrary File and Directory Deletion via CSRF

> An attacker can trick a logged-in admin into deleting arbitrary files or directories on the server via CSRF in the 3DPrint plugin.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Jan 2024
- **Updated:** 2 Jun 2025
- **Also known as:** GHSA-279h-8hwx-39m5

## What is CVE-2022-3899?

CVE-2022-3899 is a high-severity vulnerability in Unknown 3dprint, published on 16 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The 3dprint WordPress plugin before 3.5.6.9 does not protect against CSRF attacks in the modified version of Tiny File Manager included with the plugin, allowing an attacker to craft a malicious request that will delete any number of files or directories on the target server by tricking a logged in admin into submitting a form.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2022-3899?

It affects 1 product.


Products: 3dprint Project 3dprint.

## How do I fix CVE-2022-3899?

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

## Is CVE-2022-3899 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3899 exists.

## Other vulnerabilities in Unknown 3dprint

- [CVE-2022-4023](https://insights.sbomify.com/CVE-2022-4023/): 3DPrint < 3.5.6.9 - CSRF to arbitrary file downlad (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3899 and fix it if it is affected.

What it is: CVE-2022-3899 is a high-severity vulnerability in Unknown 3dprint, published on 16 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3899 exists.

Affected product: Unknown 3dprint. 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-2022-3899/ (Markdown: https://insights.sbomify.com/CVE-2022-3899/index.md)
```

## Sources

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

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