# CVE-2025-64230: WordPress Filr plugin <= 1.2.10 - Arbitrary File Deletion vulnerability

> An attacker can delete arbitrary files on the server via path traversal in the Filr plugin, potentially compromising site integrity.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H`)
- **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:** 18 Dec 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-6mm5-jg5p-3vcw

## What is CVE-2025-64230?

CVE-2025-64230 is a high-severity path traversal vulnerability in WP Chill Filr, published on 18 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in WP Chill Filr filr-protection allows Path Traversal.This issue affects Filr: from n/a through <= 1.2.10.

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

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


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

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

## Is CVE-2025-64230 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64230 is a high-severity path traversal vulnerability in WP Chill Filr, published on 18 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-64230 in the wild and no public exploit code.

Affected product: WP Chill Filr. 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-64230/ (Markdown: https://insights.sbomify.com/CVE-2025-64230/index.md)
```

## Sources

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

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