# CVE-2024-43269: WordPress Backup and Restore WordPress plugin <= 1.50 - Cross Site Request Forgery (CSRF) vulnerability

> Attackers can trick authenticated users into performing unwanted actions in the WPBackItUp Backup and Restore WordPress plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **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:** 26 Aug 2024
- **Updated:** 28 Apr 2026
- **Also known as:** CVE-2024-12208, GHSA-6c7m-rqmp-2r87

## What is CVE-2024-43269?

CVE-2024-43269 is a medium-severity vulnerability in WPBackItUp Backup and Restore WordPress, published on 26 Aug 2024. 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

Cross-Site Request Forgery (CSRF) vulnerability in WPBackItUp Backup and Restore WordPress.This issue affects Backup and Restore WordPress: from n/a through 1.50.

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

## Which versions are affected by CVE-2024-43269?

It affects 1 product.


Products: Wpbackitup Backup and Restore Wordpress.

## How do I fix CVE-2024-43269?

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

## Is CVE-2024-43269 being exploited?

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

## Other vulnerabilities in WPBackItUp Backup and Restore WordPress

- [CVE-2023-7232](https://insights.sbomify.com/CVE-2023-7232/): Backup and Restore WordPress <= 1.45 - Unauthenticated Sensitive Data Exposure (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-43269 and fix it if it is affected.

What it is: CVE-2024-43269 is a medium-severity vulnerability in WPBackItUp Backup and Restore WordPress, published on 26 Aug 2024. 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-2024-43269 in the wild and no public exploit code.

Affected product: WPBackItUp Backup and Restore WordPress. 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-2024-43269/ (Markdown: https://insights.sbomify.com/CVE-2024-43269/index.md)
```

## Sources

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

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