# CVE-2020-7241: Information disclosure in n/a

> Attackers can read database backup files by guessing predictable URLs, exposing sensitive data in the WP Database Backup plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** 20 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jqvr-gmgr-wg44

## What is CVE-2020-7241?

CVE-2020-7241 is a high-severity vulnerability in n/a, published on 20 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Database Backup plugin through 5.5 for WordPress stores downloads by default locally in the directory wp-content/uploads/db-backup/. This might allow attackers to read ZIP archives by guessing random ID numbers, guessing date strings with a 2020_{0..1}{0..2}_{0..3}{0..9} format, guessing UNIX timestamps, and making HTTPS requests with the complete guessed URL.

Weakness: CWE-330 (Use of Insufficiently Random Values)

## Which versions are affected by CVE-2020-7241?

It affects 1 product.


Products: Wpseeds Wp Database Backup.

## How do I fix CVE-2020-7241?

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

## Is CVE-2020-7241 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-25224](https://insights.sbomify.com/CVE-2019-25224/): WP Database Backup < 5.2 - Unauthenticated OS Command Injection (critical 9.8)
- [CVE-2016-10874](https://insights.sbomify.com/CVE-2016-10874/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2016-10876](https://insights.sbomify.com/CVE-2016-10876/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2016-10873](https://insights.sbomify.com/CVE-2016-10873/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2016-10875](https://insights.sbomify.com/CVE-2016-10875/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-7241 and fix it if it is affected.

What it is: CVE-2020-7241 is a high-severity vulnerability in n/a, published on 20 Jan 2020. 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-2020-7241 in the wild and no public exploit code.

Affected product: n/a. 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-2020-7241/ (Markdown: https://insights.sbomify.com/CVE-2020-7241/index.md)
```

## Sources

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

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