# CVE-2016-20076: WordPress Simple-Backup 2.7.11 Arbitrary File Deletion and Download

> Unauthenticated attackers can delete arbitrary files or download sensitive data via directory traversal in the Simple Backup plugin.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-9xr9-wq88-x9xw

## What is CVE-2016-20076?

CVE-2016-20076 is a high-severity path traversal vulnerability in ChrisHurst Simple Backup, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WordPress Simple-Backup 2.7.11 contains multiple vulnerabilities that allow unauthenticated attackers to delete arbitrary files and download sensitive files by manipulating the delete_backup_file and download_backup_file parameters in tools.php. Attackers can exploit insufficient input validation using directory traversal techniques to access wp-config.php, database dumps, and other sensitive files, or delete critical files .htaccess to expose backup directories.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2016-20076?


## How do I fix CVE-2016-20076?

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

## Is CVE-2016-20076 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-20076 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-20076 and fix it if it is affected.

What it is: CVE-2016-20076 is a high-severity path traversal vulnerability in ChrisHurst Simple Backup, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-20076 exists.

Affected product: ChrisHurst Simple Backup. 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-2016-20076/ (Markdown: https://insights.sbomify.com/CVE-2016-20076/index.md)
```

## Sources

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

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