DSGVO All in one for WP <= 4.6 - Cross-Site Request Forgery to Account Deletion
Strategic Overview
- Status
- Patched in 4.7
- Affected Plugin
- DSGVO All in one for WP
- Affected Version
<= 4.6- CVSS
- 6.5Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-13356
At a glance
CVE-2024-13356 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the DSGVO All in one for WP WordPress plugin, affecting versions <= 4.6. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 4.7; sites on affected versions should update now. Disclosed February 2025, reported by shaman0x01.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site. A successful exploit has high impact on integrity.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in DSGVO All in one for WP <= 4.6 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For DSGVO All in one for WP the fix is 4.7: builds <= 4.6 are affected, anything from 4.7 onward is not.
Remediation
Update to version 4.7, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to DSGVO All in one for WP: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: DSGVO All in one for WP 4.7 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in DSGVO All in one for WP
- 6.4CVE-2024-43964: DSGVO All in one for WP <= 4.5 Stored XSS
CVE-2024-43964 - 6.1CVE-2021-24294: DSGVO All in one for WP <= 3.9 Stored XSS
CVE-2021-24294 - 5.5CVE-2022-2628: DSGVO All in one for WP <= 4.2 Stored XSS
CVE-2022-2628 - 4.3CVE-2026-4298: DSGVO All in one for WP Authenticated (Subscriber+)
CVE-2026-4298
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C