# CVE-2025-4580: File Provider <= 1.2.3 - Item Deletion via CSRF

> Attackers can trick logged-in admins into changing File Provider plugin settings via CSRF, potentially altering file handling behavior.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **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:** 4 Jun 2025
- **Updated:** 4 Jun 2025
- **Also known as:** GHSA-hg9v-648p-2828

## What is CVE-2025-4580?

CVE-2025-4580 is a medium-severity vulnerability in Unknown File Provider, published on 4 Jun 2025. 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 File Provider WordPress plugin through 1.2.3 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack

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

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

It affects 1 product.


Products: Dimdavid File Provider.

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

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

## Is CVE-2025-4580 being exploited?

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

## Other vulnerabilities in Unknown File Provider

- [CVE-2025-4578](https://insights.sbomify.com/CVE-2025-4578/): File Provider <= 1.2.3 - Unauthenticated SQLi (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4580 is a medium-severity vulnerability in Unknown File Provider, published on 4 Jun 2025. 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-2025-4580 exists.

Affected product: Unknown File Provider. 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-4580/ (Markdown: https://insights.sbomify.com/CVE-2025-4580/index.md)
```

## Sources

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

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