# CVE-2024-11069: WordPress GDPR <= 2.0.2 - Missing Authorization to Unauthenticated Arbitrary User Deletion

> Unauthenticated attackers can delete arbitrary users due to a missing capability check in the WordPress GDPR plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Nov 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-hfp8-32jq-c2x9

## What is CVE-2024-11069?

CVE-2024-11069 is a medium-severity missing authorization vulnerability in welaunch WordPress GDPR, published on 19 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WordPress GDPR plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'WordPress_GDPR_Data_Delete::check_action' function in all versions up to, and including, 2.0.2. This makes it possible for unauthenticated attackers to delete arbitrary users.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Welaunch Wordpress Gdpr.

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

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

## Is CVE-2024-11069 being exploited?

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

## Other vulnerabilities in welaunch WordPress GDPR

- [CVE-2024-10388](https://insights.sbomify.com/CVE-2024-10388/): WordPress GDPR <= 2.0.2 - Unauthenticated Stored Cross-Site Scripting (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-11069 is a medium-severity missing authorization vulnerability in welaunch WordPress GDPR, published on 19 Nov 2024. 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-2024-11069 in the wild and no public exploit code.

Affected product: welaunch WordPress GDPR. 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-11069/ (Markdown: https://insights.sbomify.com/CVE-2024-11069/index.md)
```

## Sources

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

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