# CVE-2025-12394: Backup Migration < 2.0.0 - Unauthenticated Backup Download

> Unauthenticated attackers can download backup archives by exploiting predictable paths in specific server configurations, exposing sensitive data.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Nov 2025
- **Updated:** 24 Nov 2025
- **Also known as:** GHSA-2cmc-mfch-j64j

## What is CVE-2025-12394?

CVE-2025-12394 is a medium-severity vulnerability in Unknown Backup Migration, published on 24 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Backup Migration WordPress plugin before 2.0.0 does not properly generate its backup path in certain server configurations, allowing unauthenticated users to fetch a log that discloses the backup filename. The backup archive is then downloadable without authentication.

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


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

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

## Is CVE-2025-12394 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12394 is a medium-severity vulnerability in Unknown Backup Migration, published on 24 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-12394 in the wild and no public exploit code.

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

## Sources

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

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