dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14061

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-17
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 Cookie Banner, Cookie Consent, Consent Log, Cookie Scanner, Script Blocker (for GDPR, CCPA & ePrivacy) : WP Cookie Consent plugin for WordPress is vulnerable to unauthorized data modification due to a missing capability check on the gdpr_delete_policy_data function in all versions up to, and including, 4.0.7. This makes it possible for unauthenticated attackers to permanently delete arbitrary posts, pages, attachments, and other post types by ID.

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 Cookie Consent plugin for WordPress contains a broken access control vulnerability in the gdpr_delete_policy_data function. The function lacks a proper capability check, allowing unauthenticated attackers to permanently delete arbitrary posts, pages, attachments, and other post types by manipulating the post ID parameter.

MitigationUpdate to version 4.0.8 or later which contains the capability check fix. If immediate update is not feasible, temporarily disable the plugin or implement WAF rules to block requests to the vulnerable endpoint.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 WordPress installation
    Identify if the target site runs on WordPress by checking for wp-content/plugins/ structure or accessing /wp-admin/
    Affected if The site uses WordPress and has the vulnerable plugin installed
  2. Verify WP Cookie Consent plugin presence
    Check the WordPress plugins directory for the 'gdpr-cookie-consent' or 'wp-cookie-consent' plugin folder, or list installed plugins via WP CLI: wp plugin list --name='gdpr-cookie-consent'
    Affected if The plugin is present in the plugins directory regardless of activation status
  3. Check installed plugin version
    Read the main plugin file header for the Version field, or query via WP CLI: wp plugin get gdpr-cookie-consent --field=version
    Affected if The installed version is lower than 4.0.8 (the vulnerable versions)
  4. Confirm plugin activation status
    Check if the plugin is active via WP Admin > Plugins or via WP CLI: wp plugin is-active gdpr-cookie-consent
    Affected if The plugin is currently active on the site
  5. Test vulnerable endpoint accessibility
    Send a crafted POST request to the gdpr_delete_policy_data function endpoint (typically via admin-ajax.php with action=gdpr_delete_policy_data) with a manipulated post ID parameter, observing if deletion occurs without authentication
    Affected if The request completes successfully and deletes the specified post without requiring authentication or capability verification

The environment is affected if the WP Cookie Consent plugin is installed and active with a version earlier than 4.0.8, exposing the unauthenticated gdpr_delete_policy_data endpoint that permits arbitrary post deletion.

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 to version 4.0.8 or later which contains the capability check fix. If immediate update is not feasible, temporarily disable the plugin or implement WAF rules to block requests to the vulnerable endpoint.

Recommended fix Moderate confidence

Version 4.0.8 or later of the WP Cookie Consent plugin

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'WP Cookie Consent' (also known as Cookie Banner, Cookie Consent, Consent Log, Cookie Scanner, Script Blocker)
  4. Check if the current version is 4.0.7 or below
  5. If vulnerable, click 'Update Now' or download the latest version from wordpress.org and upload it
  6. Verify the update completes successfully
  7. Confirm the new version is 4.0.8 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,520
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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