Wordpress GdprWordPress extension · Welaunch
CVE-2024-11069
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe WordPress GDPR plugin fails to enforce authorization checks on the WordPress_GDPR_Data_Delete::check_action function, allowing unauthenticated attackers to send crafted requests that delete any user account on the WordPress site. This is a critical IDOR (Insecure Direct Object Reference) vulnerability due to missing capability verification.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wordpress GdprWordPress extension
< 2.0.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm GDPR plugin is installedAccess WordPress Admin > Plugins and look for any plugin containing 'GDPR' in the name, specifically the 'Welaunch Wordpress Gdpr' pluginAffected if Plugin appears in the installed plugins list
-
Check installed plugin versionIn WordPress Admin > Plugins, click on the GDPR plugin to view its details and read the Version number, or inspect the main plugin PHP file for the 'Version' header in the plugin comment blockAffected if Version number is less than 2.0.3
-
Identify vulnerable functionSearch the plugin directory for the file containing 'WordPress_GDPR_Data_Delete' class and locate the 'check_action' method inside itAffected if The check_action function exists in the plugin code
The environment is affected if the Welaunch Wordpress Gdpr plugin is installed with a version prior to 2.0.3, as this version range lacks proper capability verification in the user deletion function
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.0.3
Update the plugin to version 2.0.3 or later which includes proper capability checks. If no patch is available, disable the plugin immediately to prevent unauthenticated user deletion attacks.
WordPress GDPR plugin version 2.0.3
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Find the 'WordPress GDPR' plugin in the list
- 4. If an update is available, click 'Update Now' to upgrade to version 2.0.3
- 5. Alternatively, manually upload the plugin version 2.0.3 from the WordPress plugin repository or vendor
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wordpress Gdpr
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11069 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-11069 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data