dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-68073

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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.4.

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 Ninja Team GDPR CCPA Compliance Support WordPress plugin (versions <= 2.7.4) contains a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This likely enables unauthorized users to access or modify GDPR/CCPA compliance settings and data that should require administrative privileges.

MitigationUpdate the plugin to the latest version which should include proper capability checks (current_user_can()) and authorization validation for all sensitive functions. If no patch is available, temporarily disable the plugin until a fix is released.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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. Identify if the affected plugin is installed
    Access your WordPress admin panel, go to Plugins > Installed Plugins, and look for 'Ninja Team GDPR CCPA Compliance Support' or check the /wp-content/plugins/ directory for a folder containing 'gdpr-ccpa' or 'ninja-team' in the name
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    In WordPress admin, view the plugin details to see the version number, or check the plugin's main PHP file for the 'Version' header in the plugin comment block
    Affected if The version number is 2.7.4 or lower
  3. Verify if admin AJAX actions lack capability checks
    Examine the plugin's main PHP file for AJAX handlers (wp_ajax_ hooks) and check if they include current_user_can() or similar capability checks before executing sensitive operations
    Affected if AJAX endpoints exist without current_user_can() validation or other authorization checks
  4. Test for unauthorized access to compliance settings
    Using a low-privileged user account (subscriber or contributor role), attempt to access the plugin's admin pages directly via URL or submit requests to its settings endpoints
    Affected if A non-administrator user can access or modify GDPR/CCPA compliance settings without being prompted for authorization

Your environment is affected if the Ninja Team GDPR CCPA Compliance Support plugin is installed at version 2.7.4 or lower and its admin functions/settings are accessible to users without administrative privileges.

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 plugin to the latest version which should include proper capability checks (current_user_can()) and authorization validation for all sensitive functions. If no patch is available, temporarily disable the plugin until a fix is released.

Recommended fix Moderate confidence

Latest version of GDPR CCPA Compliance Support (newer than 2.7.4)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'GDPR CCPA Compliance Support' by Ninja Team
  4. Check if an update is available and install the latest version

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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