dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-10034

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 authorization bypass in all versions up to, and including, 3.1.39. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to supply an arbitrary victim email address and trigger immediate SAR processing via the process_now and is_ajax parameters, receiving tokenized download links (zip_link, pdf_link) in the HTTP response that expose the victim's personal data — including WordPress account details, comment author names, email addresses, IP addresses, and comment content — without any proof of ownership. The nonce used for the CSRF check is publicly rendered by the SAR shortcode form and is shared across all anonymous visitors, meaning any unauthenticated attacker can trivially obtain a valid nonce and bypass this gate entirely.

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.39 contain an authorization bypass vulnerability where the plugin fails to verify that users are authorized to request personal data. Unauthenticated attackers can obtain a publicly-rendered nonce from the SAR form, then use it to trigger SAR processing via the process_now and is_ajax parameters with any victim email address, receiving tokenized download links that expose the victim's personal data including WP account details, comment author names, emails, IPs, and comment content.

MitigationUpgrade to a patched version of the plugin that implements proper authorization verification, ensures nonces are not shared across anonymous visitors, and requires proof of ownership before releasing personal data via SAR requests.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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. Confirm WP DSGVO Tools plugin is installed
    Check your WordPress plugins directory or wp-admin plugins list for 'WP DSGVO Tools (GDPR)' or 'DSGVO Tools'
    Affected if The plugin is installed and appears in your WordPress plugins list
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > WP DSGVO Tools (GDPR) and note the version number displayed
    Affected if The version number is 3.1.39 or lower
  3. Verify SAR feature is enabled
    Navigate to the plugin settings in WordPress admin (typically under DSGVO/GDPR settings) and check if the SAR (Subject Access Request / Right to Access) feature is activated
    Affected if SAR functionality is enabled in the plugin configuration
  4. Test SAR form accessibility
    Visit the public SAR request form on your site (usually at /?page_id=XX with SAR form shortcode, or check for a frontend form with fields for email request) while logged out (unauthenticated)
    Affected if The SAR form is publicly accessible without authentication
  5. Inspect SAR form for nonce exposure
    View the page source of the public SAR form and search for hidden form fields containing 'nonce' or '_wpnonce' values that are rendered for anonymous visitors
    Affected if A nonce value is rendered in the HTML for unauthenticated users on the SAR form

If the WP DSGVO Tools plugin version is 3.1.39 or lower, the SAR feature is enabled, and the plugin exposes nonce values to unauthenticated visitors on the SAR form, then your environment is affected by this authorization bypass vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of the plugin that implements proper authorization verification, ensures nonces are not shared across anonymous visitors, and requires proof of ownership before releasing personal data via SAR requests.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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