dbcve.org
Gdpr Ccpa Compliance \& Cookie Consent BannerWordPress extension · Ninjateam

CVE-2025-24591

HIGH · 8.8 CVSS v3.1 Published 2025-01-24
Fix available
A fix is available. Upgrade to 2.7.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Ninja Team GDPR CCPA Compliance Support ninja-gdpr-compliance allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects GDPR CCPA Compliance Support: from n/a through <= 2.7.1.

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

Missing authorization vulnerability in the GDPR CCPA Compliance Support plugin allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthenticated or low-privileged users to access or modify compliance settings they should not have permission to access.

MitigationUpdate the plugin to the latest version which implements proper authorization checks at function level, or if no update is available, implement server-side access control validation for all sensitive compliance functions.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Gdpr Ccpa Compliance \& Cookie Consent BannerWordPress extension
Affected:< 2.7.2

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Identify installed plugin version
    Locate the plugin files in your WordPress wp-content/plugins directory under 'gdpr-ccpa-compliance' or similar naming, then check the main plugin PHP file for the version constant or header
    Affected if The version listed is less than 2.7.2
  2. Verify plugin is active
    Check the WordPress database wp_options table for the option 'active_plugins' or use wp-cli 'wp plugin list' to confirm the GDPR CCPA Compliance plugin is currently activated
    Affected if The plugin is active and running a vulnerable version below 2.7.2
  3. Inspect admin AJAX hooks
    Examine the plugin's main PHP file for add_action calls registering wp_ajax_ hooks, noting which hooks lack capability checks or nonce verification
    Affected if AJAX endpoints exist that perform sensitive compliance functions without checking user capabilities
  4. Check admin page access controls
    Review plugin code for admin menu registration (add_menu_page) and verify that callback functions include current_user_can() capability checks before displaying or modifying settings
    Affected if Admin pages or settings panels load without verifying the current user has administrator privileges
  5. Review stored compliance settings
    Query the wp_options table for option_name values related to the plugin (often prefixed with 'ninjateam_gdpr' or similar) to understand what compliance data is stored
    Affected if Compliance settings can be modified by users lacking proper permissions, indicating broken access control

Your environment is affected if the Ninjateam GDPR CCPA Compliance plugin version is below 2.7.2 and the plugin is active with unprotected AJAX endpoints or admin pages that allow low-privileged users to modify compliance settings.

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
Upgrade available Upgrade to 2.7.2 or later
Fixed in 2.7.2
Interim mitigation

Update the plugin to the latest version which implements proper authorization checks at function level, or if no update is available, implement server-side access control validation for all sensitive compliance functions.

Recommended fix High confidence

Version 2.7.2 or latest available version of GDPR CCPA Compliance Support (ninja-gdpr-compliance)

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'GDPR CCPA Compliance & Cookie Consent Banner' by Ninja Team
  4. If an update is available, click 'Update Now' to update to version 2.7.2 or the latest version
  5. Alternatively, you can manually download version 2.7.2 or latest from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin version shows 2.7.2 or higher in the installed plugins list
  7. Review plugin settings to ensure authorization controls are functioning correctly

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

Fix this in Gdpr Ccpa Compliance \& Cookie Consent Banner 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 the upgrade done

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-2025-24591 — 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-24591 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