# CVE-2026-86826: BackWPup < 5.7.7 - Unauthenticated Sensitive Data Disclosure via Restore Working Directory on NGINX

> Unauthenticated attackers can download sensitive backup archives containing credentials and site files if the web server does not honor .htaccess rules.

- **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:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-jprm-wgx9-37wq

## What is CVE-2026-86826?

CVE-2026-86826 is a medium-severity vulnerability in Unknown BackWPup, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The BackWPup  WordPress plugin before 5.7.7 does not properly restrict web access to the working directory it uses during backup restores, allowing unauthenticated attackers, on webservers that do not honour .htaccess rules such as NGINX, to download the full backup archive (database dump and site files, including credentials and secret keys) left behind by an interrupted restore.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-86826 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86826 is a medium-severity vulnerability in Unknown BackWPup, published on 8 Oct 2026. 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-2026-86826 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-86826/ (Markdown: https://insights.sbomify.com/CVE-2026-86826/index.md)
```

## Sources

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

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