dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-11754

HIGH · 7.5 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 GDPR Cookie Consent plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'gdpr/v1/settings' REST API endpoint in all versions up to, and including, 4.1.2. This makes it possible for unauthenticated attackers to retrieve sensitive plugin settings including API tokens, email addresses, account IDs, and site keys.

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 GDPR Cookie Consent WordPress plugin fails to enforce authorization on its REST API endpoint 'gdpr/v1/settings', allowing any unauthenticated user to retrieve sensitive configuration data including API tokens, email addresses, account IDs, and site keys. This occurs because the endpoint lacks a capability check (permission_callback) to verify the requester's permissions.

MitigationUpdate the GDPR Cookie Consent plugin to version 4.1.3 or later, which includes proper capability checks on the REST API endpoint. Until updated, consider disabling the REST API or restricting access at the server level.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 plugin installation and version
    Navigate to WordPress admin > Plugins and locate 'GDPR Cookie Consent' or check the plugin file header in wp-content/plugins/gdpr-cookie-consent/readme.txt for the Version field
    Affected if The plugin is installed and the version is lower than 4.1.3
  2. Test unauthenticated REST API access
    Send a GET request to https://yourdomain.com/wp-json/gdpr/v1/settings without providing any authentication credentials (no nonce, no session)
    Affected if The endpoint returns a 200 OK response with JSON data containing sensitive fields such as api_token, email_address, account_id, or site_key
  3. Verify sensitive data exposure
    Examine the JSON response from the previous request for the presence of configuration values like 'api_token', 'account_id', 'site_key', or email addresses
    Affected if The response contains any plaintext API tokens, account IDs, site keys, or email addresses associated with the plugin configuration
  4. Check permission_callback implementation
    Inspect the plugin's REST API registration code (typically in includes/class-gdpr-cookie-consent.php or similar) for the gdpr/v1/settings endpoint registration and verify if permission_callback is defined and enforces authentication
    Affected if The endpoint registration lacks a permission_callback or the callback always returns true, allowing any requester to access the data

You are affected if the GDPR Cookie Consent plugin version is below 4.1.3 AND the /wp-json/gdpr/v1/settings endpoint responds to unauthenticated requests with sensitive configuration data.

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

Update the GDPR Cookie Consent plugin to version 4.1.3 or later, which includes proper capability checks on the REST API endpoint. Until updated, consider disabling the REST API or restricting access at the server level.

Recommended fix High confidence

4.1.3 or latest available version

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'GDPR Cookie Consent' plugin
  4. 4. Check the current installed version (should be 4.1.2 or lower)
  5. 5. Click 'Update now' if an update to version 4.1.3 or higher is available
  6. 6. Alternatively, download the latest version from wordpress.org/plugins/gdpr-cookie-consent/ and upload via Plugins > Add New > Upload Plugin
  7. 7. After updating, verify the REST API endpoint 'gdpr/v1/settings' now requires authentication

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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