# CVE-2025-8213: NinjaScanner – Virus & Malware scan <= 3.2.5 - Authenticated (Administrator+) Arbitrary File Deletion

> Authenticated administrators can delete arbitrary files on the server due to insufficient path validation in the NinjaScanner WordPress plugin.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-j98h-m6px-h428

## What is CVE-2025-8213?

CVE-2025-8213 is a high-severity path traversal vulnerability in nintechnet NinjaScanner – Virus & Malware scan, published on 31 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The NinjaScanner – Virus & Malware scan plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the 'nscan_ajax_quarantine' and 'nscan_quarantine_select' functions in all versions up to, and including, 3.2.5. This makes it possible for authenticated attackers, with Administrator-level access and above, to delete arbitrary files on the server, including files outside the WordPress root directory.

Weakness: CWE-36 (Absolute Path Traversal)

## Which versions are affected by CVE-2025-8213?


## How do I fix CVE-2025-8213?

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

## Is CVE-2025-8213 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8213 and fix it if it is affected.

What it is: CVE-2025-8213 is a high-severity path traversal vulnerability in nintechnet NinjaScanner – Virus & Malware scan, published on 31 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-8213 in the wild and no public exploit code.

Affected product: nintechnet NinjaScanner – Virus & Malware scan. 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-2025-8213/ (Markdown: https://insights.sbomify.com/CVE-2025-8213/index.md)
```

## Sources

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

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