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

CVE-2024-27967

HIGH · 8.8 CVSS v3.1 Published 2024-04-11
Fix available
A fix is available. Upgrade to 4.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Michael Leithold DSGVO All in one for WP.This issue affects DSGVO All in one for WP: from n/a through 4.3.

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

Cross-Site Request Forgery (CSRF) vulnerability in the DSGVO All in one for WP WordPress plugin (versions through 4.3) allows attackers to trick authenticated administrators into performing unintended state-changing actions, such as modifying plugin settings or executing administrative functions, due to missing or inadequate anti-CSRF token validation.

MitigationAdd WordPress nonces (anti-CSRF tokens) to all form submissions, admin action hooks, and AJAX endpoints; verify nonce validity before processing any state-changing requests.

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.4

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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 checks

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

  1. Verify the plugin is installed
    Log in to WordPress admin, go to Plugins > Installed Plugins, and look for 'DSGVO All in one for WP' or 'Dsgvo For Wp Dsgvo All In One For Wp' in the list of active or installed plugins.
    Affected if The plugin appears in the installed plugins list.
  2. Check the installed version number
    In WordPress admin, go to Plugins > Installed Plugins, find the DSGVO plugin, and note the version number displayed below the plugin name.
    Affected if The version is 4.3 or lower, or any version below 4.4.
  3. Confirm via plugin files if accessible
    If you have file system access, check the main plugin file (typically named dsgvo-all-in-one-for-wp.php or similar in wp-content/plugins/) for the version header comment, or check the plugin's main PHP file for the Version constant or defined value.
    Affected if The version read from the plugin files is less than 4.4.
  4. Check for state-changing admin actions
    Review the plugin settings pages and admin menu items to identify any forms or action URLs that perform state-changing operations such as saving settings, updating options, or executing administrative functions.
    Affected if The plugin has admin forms or action hooks that process requests without explicit nonce verification.

If the DSGVO All in one for WP plugin is installed and the version is below 4.4, the environment is affected by this CSRF vulnerability due to missing anti-CSRF token validation.

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 4.4 or later
Fixed in 4.4
Interim mitigation

Add WordPress nonces (anti-CSRF tokens) to all form submissions, admin action hooks, and AJAX endpoints; verify nonce validity before processing any state-changing requests.

Recommended fix Moderate confidence

4.4

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'DSGVO All in one for WP' in the list
  4. If an update is available, click 'Update Now' to update to version 4.4
  5. Alternatively, download version 4.4 from the official WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin is running version 4.4 by checking the Plugins list

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-27967 — 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-27967 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