# CVE-2025-10579: BackWPup <= 5.5.0 - Missing Authorization to Sensitive Information Exposure

> Authenticated attackers can retrieve backup filenames via a missing capability check, potentially aiding brute-force attacks to access backup contents.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 25 Oct 2025
- **Updated:** 27 Oct 2025
- **Also known as:** GHSA-vq3q-xwqw-cc8c

## What is CVE-2025-10579?

CVE-2025-10579 is a medium-severity missing authorization vulnerability in wp_media BackWPup – WordPress Backup & Restore Plugin, published on 25 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The BackWPup – WordPress Backup & Restore Plugin plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'backwpup_working' AJAX action in all versions up to, and including, 5.5.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve access to a back-up's filename while a backup is running. This information has little value on it's own, but could be used to aid in a brute force attack to retrieve back-up contents in limited environments (i.e. NGINX).

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-10579 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10579 is a medium-severity missing authorization vulnerability in wp_media BackWPup – WordPress Backup & Restore Plugin, published on 25 Oct 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-10579 in the wild and no public exploit code.

Affected product: wp_media BackWPup – WordPress Backup & Restore Plugin. 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-10579/ (Markdown: https://insights.sbomify.com/CVE-2025-10579/index.md)
```

## Sources

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

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