dbcve.org
Dsgvo All In One For WpWordPress extension · Dsgvo For Wp

CVE-2024-43964

MEDIUM · 5.4 CVSS v3.1 Published 2024-08-29
Fix available
A fix is available. Upgrade to after 4.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Michael Leithold DSGVO All in one for WP allows Stored XSS.This issue affects DSGVO All in one for WP: from n/a through 4.5.

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 · moderate confidence

Stored XSS vulnerability in the DSGVO All in one for WP WordPress plugin allows attackers to inject malicious JavaScript through unsanitized user input that gets stored in the database and executed when other users view the affected pages.

MitigationUpdate the plugin to the latest version once available, or implement proper input sanitization and output encoding for all user-supplied data before rendering in HTML contexts.

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
Dsgvo All In One For WpWordPress extension
Affected:<= 4.5

CVSS 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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check the installed plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins and locate 'DSGVO All in one for WP' (also labeled as 'Dsgvo For Wp Dsgvo All In One For Wp'), or inspect the plugin main file header in wp-content/plugins/dsgvo-all-in-one-for-wp/
    Affected if The displayed version is 4.5 or any lower version number (e.g., 4.4, 4.3, etc.)
  2. Identify plugin settings pages that accept user input
    Access the plugin settings pages in WordPress admin (typically found under 'DSGVO' or 'Privacy' menu items added by the plugin) and review all form fields where data can be submitted and saved
    Affected if The plugin settings pages contain input fields that save data to the database without visible sanitization indicators or that allow HTML/script tags to be stored and retrieved
  3. Inspect stored plugin data in the database
    Query the WordPress database (wp_options table or plugin-specific tables) for any records containing the plugin prefix, looking for values that include script tags, javascript: URIs, or event handler attributes like onload, onerror, onclick
    Affected if Database entries related to the plugin contain raw HTML, script tags, or JavaScript event handlers that were not stripped or encoded during storage
  4. Verify output encoding in plugin frontend rendering
    View the source code of any frontend pages where the plugin displays user-configured text (e.g., cookie consent banners, privacy policy text, consent checkboxes) and check if special characters are encoded as HTML entities (e.g., < as &lt;, > as &gt;)
    Affected if User-supplied text from plugin settings is rendered in HTML context without proper encoding, allowing stored scripts to execute when page loads

You are affected if the installed plugin version is 4.5 or lower AND any user-configurable plugin settings allow storing unsanitized input that renders as executable HTML/JavaScript in browser contexts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 4.5
Interim mitigation

Update the plugin to the latest version once available, or implement proper input sanitization and output encoding for all user-supplied data before rendering in HTML contexts.

Recommended fix Moderate confidence

Version 4.6 or later (check WordPress plugin repository for latest stable release)

  1. Check the current version of DSGVO All in One For WP plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Locate DSGVO All in one for WP and note the current version number
  4. Visit the official WordPress plugin repository or the plugin developer's website to check for the latest version
  5. If version 4.6 or higher is available, update the plugin through Plugins > Installed Plugins > Update Now
  6. If no update is available, consider disabling and removing the plugin until a security patch is released
  7. If you must continue using the plugin without an update, implement additional input sanitization at the web application firewall (WAF) level to filter malicious scripts
  8. After updating, verify the fix by testing that the XSS payload can no longer be executed
Caveat Minimal risk - this is a security patch update, but always test updates in a staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dsgvo All In One For Wp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43964 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-43964 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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