dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-66080

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-30
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
Missing Authorization vulnerability in WP Legal Pages WP Cookie Notice for GDPR, CCPA & ePrivacy Consent gdpr-cookie-consent allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Cookie Notice for GDPR, CCPA & ePrivacy Consent: from n/a through <= 4.0.3.

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

The WP Cookie Notice for GDPR, CCPA & ePrivacy Consent WordPress plugin versions <= 4.0.3 contains a missing authorization vulnerability that allows exploiting incorrectly configured access control security levels. This likely permits unauthenticated or lower-privileged users to access administrative functionality or perform actions that should require higher privileges.

MitigationImplement proper capability checks and authorization verification for all sensitive functions and AJAX endpoints in the plugin, ensuring that user roles and permissions are correctly validated before executing privileged operations.

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

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

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. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Cookie Notice for GDPR, CCPA & ePrivacy Consent'. The version number is displayed below the plugin name. Alternatively, inspect the main plugin file header (usually in the plugin root directory) to find the 'Version' comment.
    Affected if The installed version is 4.0.3 or any earlier version (e.g., 4.0.2, 4.0.1, 4.0.0, etc.)
  2. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify that the WP Cookie Notice plugin has an 'Active' status under the plugin name.
    Affected if The plugin is installed and active on the WordPress site
  3. Identify accessible AJAX endpoints
    Inspect the plugin source code files (typically in the plugin directory under /includes or /admin folder) for registered AJAX actions using add_action('wp_ajax_...') and add_action('wp_ajax_nopriv_...'). Look for any endpoints that handle administrative operations or sensitive data.
    Affected if The plugin registers AJAX endpoints that handle privileged operations without proper capability checks (such as checking current_user_can() or similar authorization functions)
  4. Test for unauthorized access to admin functions
    If you have access to a low-privilege test account (subscriber or contributor role) or can test as an unauthenticated user, attempt to access any cookie notice settings pages or trigger any AJAX actions exposed by the plugin.
    Affected if Lower-privileged users or unauthenticated visitors can access settings pages, modify cookie consent configurations, or execute administrative functions that should require administrator privileges

If the plugin version is 4.0.3 or lower AND the plugin is active, the missing authorization vulnerability is likely present regardless of which specific endpoint is exploitable.

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

Implement proper capability checks and authorization verification for all sensitive functions and AJAX endpoints in the plugin, ensuring that user roles and permissions are correctly validated before executing privileged operations.

Recommended fix Moderate confidence

Plugin version 4.0.4 or later

  1. Check your WordPress site's installed plugins to confirm the current version of WP Cookie Notice for GDPR, CCPA & ePrivacy Consent
  2. Navigate to Plugins > Add New > Upload or update through the WordPress plugin repository
  3. Update the plugin to the latest available version (after 4.0.3)
  4. Verify the update completed successfully
  5. Test that the cookie consent functionality still works as expected on your site
  6. Confirm that the authorization controls are now properly enforced

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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