Plugins · dsgvo-all-in-one-for-wp · data as of 2026-11-04
Is DSGVO All in one for WP safe? Known vulnerabilities and latest version
- Status
- Closed 2026-10-23
- Known issues on record
- 7
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate dsgvo-all-in-one-for-wp && wp plugin delete dsgvo-all-in-one-for-wp
Check your version
Known vulnerabilities
7 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 7 record(s) do not state which versions are affected.
high 7.2 CVE-2026-96741 · published 2026-10-29
Stored cross-site scripting (XSS) in DSGVO All in one for WP (5.0 and older)
- Affected
- 5.0 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The DSGVO All in one for WP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content via Output Buffer Regex Corruption in all versions up to, and including, 5.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is only exploitable when the administrator has enabled both the 'Google Tag Manager' integration and the 'Replace integration automatically [Beta]' option, and requires the crafted comment to be approved by an administrator.
medium 4.3 CVE-2026-4298 · published 2026-07-09
Missing authorization check in DSGVO All in one for WP (4.9 and older)
- Affected
- 4.9 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The DSGVO All in one for WP plugin for WordPress is vulnerable to Missing Authorization in all versions up to and including 4.9. This is due to the dsgvo_reset_policy_service_func() function lacking both capability checks and nonce verification while processing user-supplied parameters to reset plugin options. This makes it possible for authenticated attackers, with Subscriber-level access and above, to reset all customized privacy policy content including cookie notices, Google Analytics policies, Facebook policies, and YouTube policies to their default values.
NVD CVE-2026-4298Wordfence advisoryCode change (fix)Plugin source
medium 6.5 CVE-2024-13356 · published 2025-02-04
Cross-site request forgery (CSRF) in DSGVO All in one for WP (4.6 and older)
- Affected
- 4.6 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The DSGVO All in one for WP plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.6. This is due to missing or incorrect nonce validation in the user_remove_form.php file. This makes it possible for unauthenticated attackers to delete admin user accounts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
NVD CVE-2024-13356Wordfence advisoryCode change (fix)Plugin source
medium 5.4 CVE-2024-43964 · published 2024-08-29
Stored cross-site scripting (XSS) in DSGVO All in one for WP (4.5 and older)
- Affected
- 4.5 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
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.
high 8.8 CVE-2024-27967 · published 2024-04-11
Cross-site request forgery (CSRF) in DSGVO All in one for WP (4.3 and older)
- Affected
- 4.3 and older
- Fixed in
- 4.4
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
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.
medium 4.8 CVE-2022-2628 · published 2022-10-03
Stored cross-site scripting (XSS) in DSGVO All in one for WP (older than 4.2)
- Affected
- older than 4.2
- Fixed in
- 4.2
- Access needed (per CVSS)
- Needs an admin-level account; someone on the site has to click a link or open a page
- Range from
- NVD analysis · score by NVD
Details from the advisory
The DSGVO All in one for WP WordPress plugin before 4.2 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)
medium 6.1 CVE-2021-24294 · published 2021-05-24
Cross-site scripting (XSS) in DSGVO All in one for WP (older than 4.0)
- Affected
- older than 4.0
- Fixed in
- 4.0
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- NVD analysis · score by NVD
Details from the advisory
The dsgvoaio_write_log AJAX action of the DSGVO All in one for WP WordPress plugin before 4.0 did not sanitise or escape some POST parameter submitted before outputting them in the Log page in the administrator dashboard (wp-admin/admin.php?page=dsgvoaiofree-show-log). This could allow unauthenticated attackers to gain unauthorised access by using an XSS payload to create a rogue administrator account, which will be trigged when an administrator will view the logs.
Recent activity
- 2026-10-23 — closed on wordpress.org.
- 2026-10-29 — Stored cross-site scripting (XSS) disclosed (CVE-2026-96741), fix version not stated.
- 2026-07-09 — Missing authorization check disclosed (CVE-2026-4298), fix version not stated.
- 2025-02-04 — Cross-site request forgery (CSRF) disclosed (CVE-2024-13356), fix version not stated.
Get an email when DSGVO All in one for WP has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for DSGVO All in one for WP (dsgvo-all-in-one-for-wp) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Cross-site scripting (XSS) (4) · Cross-site request forgery (CSRF) (2) · Missing authorization (1)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/dsgvo-all-in-one-for-wp (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/dsgvo-all-in-one-for-wp"><img src="https://laskyr.com/plugins/dsgvo-all-in-one-for-wp/badge.svg" alt="DSGVO All in one for WP vulnerability status"></a>