dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-4283

CRITICAL · 9.1 CVSS v3.1 Published 2026-03-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
The WP DSGVO Tools (GDPR) plugin for WordPress is vulnerable to unauthorized account destruction in all versions up to, and including, 3.1.38. This is due to the `super-unsubscribe` AJAX action accepting a `process_now` parameter from unauthenticated users, which bypasses the intended email-confirmation flow and immediately triggers irreversible account anonymization. This makes it possible for unauthenticated attackers to permanently destroy any non-administrator user account (password randomized, username/email overwritten, roles stripped, comments anonymized, sensitive usermeta wiped) by submitting the victim's email address with `process_now=1`. The nonce required for the request is publicly available on any page containing the `[unsubscribe_form]` shortcode.

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

The WP DSGVO Tools (GDPR) WordPress plugin versions up to 3.1.38 contain an insecure direct object reference (IDOR) vulnerability in the `super-unsubscribe` AJAX action. The action accepts a `process_now` parameter from any unauthenticated request, bypassing the intended email-confirmation flow. Since the nonce is publicly exposed on pages containing the `[unsubscribe_form]` shortcode, attackers can submit arbitrary email addresses with `process_now=1` to trigger irreversible account anonymization (password randomization, username/email overwrite, role stripping, comment anonymization, usermeta deletion).

MitigationImmediately update to version 3.1.39 or later which patches this vulnerability. Until then, consider disabling the `[unsubscribe_form]` shortcode or implementing web application firewall (WAF) rules to block suspicious `super-unsubscribe` requests with the `process_now` parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 WP DSGVO Tools plugin is installed
    Check the WordPress plugin directory for the 'wp-dsgvo-tools' folder in wp-content/plugins/, or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if The plugin named 'WP DSGVO Tools (GDPR)' or similar is present in the installation
  2. Determine installed plugin version
    Open the main plugin PHP file (typically named similar to ds-gvo-tools.php or wp-dsgvo-tools.php) in the plugin folder and check the 'Version:' header in the file comments, or view in WordPress admin under Plugins > Installed Plugins > Plugin Details
    Affected if Version is 3.1.38 or lower (any version up to and including 3.1.38)
  3. Check for [unsubscribe_form] shortcode usage
    Search the WordPress database for the shortcode '[unsubscribe_form]' in the wp_posts table content field, or manually inspect published pages and posts in the WordPress admin editor for the presence of [unsubscribe_form]
    Affected if The shortcode is present on any published page, post, or widget
  4. Test AJAX endpoint accessibility
    Send a crafted POST request to /wp-admin/admin-ajax.php with parameters action=super-unsubscribe and process_now=1 (optionally with an email parameter), either via curl, Burp Suite, or a similar HTTP client. No authentication or valid nonce should be required for successful submission
    Affected if The request completes without requiring email confirmation or returning an authentication/nonce error

If the plugin is installed with version 3.1.38 or lower and the [unsubscribe_form] shortcode is in use, the vulnerable AJAX endpoint is exposed and the environment is affected by this CVE.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately update to version 3.1.39 or later which patches this vulnerability. Until then, consider disabling the `[unsubscribe_form]` shortcode or implementing web application firewall (WAF) rules to block suspicious `super-unsubscribe` requests with the `process_now` parameter.

Recommended fix Moderate confidence

3.1.39 or latest available version

  1. 1. Update the WP DSGVO Tools (GDPR) plugin to the latest version available in the WordPress plugin repository.
  2. 2. After updating, verify that the `[unsubscribe_form]` shortcode pages no longer expose the nonce in an exploitable manner.
  3. 3. Review user accounts to ensure no unauthorized account destruction has occurred.
  4. 4. Consider implementing additional server-side access controls as a defensive measure.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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