DSGVO All in one for WP <= 4.9 - Missing Authorization to Authenticated (Subscriber+) Settings Reset
Strategic Overview
- Status
- Patched in 5.0
- Affected Plugin
- DSGVO All in one for WP
- Affected Version
<= 4.9- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-4298
At a glance
CVE-2026-4298 is a medium-severity Missing Authorization vulnerability in the DSGVO All in one for WP WordPress plugin, affecting versions <= 4.9. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 5.0; sites on affected versions should update now. Disclosed July 2026, reported by nudien udin.
Vulnerability Overview
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.
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 interaction from a victim user.
CWE-862: Missing Authorization
DSGVO All in one for WP <= 4.9 carries this weakness at dsgvo_reset_policy_service_func(), and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For DSGVO All in one for WP the fix is 5.0: builds <= 4.9 are affected, anything from 5.0 onward is not.
Remediation
Update to version 5.0, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: DSGVO All in one for WP 5.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in DSGVO All in one for WP
- 6.5CVE-2024-13356: DSGVO All in one for WP CSRF to Account Deletion
CVE-2024-13356 - 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-2024-27967: DSGVO All in one for WP <= 4.3 CSRF
CVE-2024-27967
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C