# CVE-2026-86815: Missing authorization in BackWPup

> Attackers with limited plugin roles can exfiltrate full database backups via unrestricted REST API routes in BackWPup.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-qr55-6j78-v53m

## What is CVE-2026-86815?

CVE-2026-86815 is a medium-severity missing authorization vulnerability in Unknown BackWPup, published on 11 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The BackWPup  WordPress plugin before 5.7.5 does not properly restrict access to several of its REST API routes for job, backup-destination, and backup-execution management, allowing users holding a BackWPup  WordPress plugin before 5.7.5-defined, administrator-assigned limited role to create and run backup jobs and exfiltrate a full database backup to an attacker-controlled destination.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-86815?


## How do I fix CVE-2026-86815?

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

## Is CVE-2026-86815 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-86815 and fix it if it is affected.

What it is: CVE-2026-86815 is a medium-severity missing authorization vulnerability in Unknown BackWPup, published on 11 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86815 in the wild and no public exploit code.

Affected product: Unknown BackWPup. 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-2026-86815/ (Markdown: https://insights.sbomify.com/CVE-2026-86815/index.md)
```

## Sources

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

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