# CVE-2020-36669: JetBackup – WP Backup, Migrate & Restore <= 1.3.9 - Cross-Site Request Forgery to Arbitrary File Upload

> Unauthenticated attackers can upload arbitrary files via CSRF by tricking administrators, potentially leading to code execution on WordPress sites using JetBackup.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Mar 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-2m88-5j35-4r5m

## What is CVE-2020-36669?

CVE-2020-36669 is a high-severity vulnerability in backupguard JetBackup – Backup, Restore & Migrate, published on 7 Mar 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The JetBackup – WP Backup, Migrate & Restore plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including 1.3.9. This is due to missing nonce validation on the backup_guard_get_import_backup() function. This makes it possible for unauthenticated attackers to upload arbitrary files to the vulnerable site's server via a forged request, granted they can trick a site's administrator into performing an action such as clicking on a link.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Jetbackup Jetbackup.

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

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

## Is CVE-2020-36669 being exploited?

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

## Other vulnerabilities in backupguard JetBackup – Backup, Restore & Migrate

- [CVE-2023-7165](https://insights.sbomify.com/CVE-2023-7165/): JetBackup < 2.0.9.9 - Directory Listing Exposing Backups (high 7.5)
- [CVE-2020-36667](https://insights.sbomify.com/CVE-2020-36667/): JetBackup – WP Backup, Migrate & Restore <= 1.4.1 - Missing Authorization to Unauthorized Backup Location Change (medium 5.4)
- [CVE-2022-34148](https://insights.sbomify.com/CVE-2022-34148/): WordPress Backup Guard Plugin <= 1.6.9.0 is vulnerable to Cross Site Scripting (XSS) (medium 4.8)
- [CVE-2020-36668](https://insights.sbomify.com/CVE-2020-36668/): JetBackup – WP Backup, Migrate & Restore <= 1.4.0 - Sensitive Information Disclosure (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-36669 is a high-severity vulnerability in backupguard JetBackup – Backup, Restore & Migrate, published on 7 Mar 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-36669 in the wild and no public exploit code.

Affected product: backupguard JetBackup – Backup, Restore & Migrate. 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-36669/ (Markdown: https://insights.sbomify.com/CVE-2020-36669/index.md)
```

## Sources

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

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