dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2025-3014

HIGH · 8.3 CVSS v4.0 Published 2025-03-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
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
Insecure Direct Object References (IDOR) in access control in Tracking 2.1.4 on NightWolf Penetration Testing allows an attacker to access via manipulating request parameters or object references.

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

IDOR vulnerability in the access control mechanism of Tracking component version 2.1.4 within NightWolf Penetration Testing. Attackers can manipulate request parameters or object references (such as database IDs or resource identifiers) to bypass authorization and access sensitive data or functionality they are not permitted to view or modify.

MitigationImplement proper authorization validation on all object references by verifying the current user's permissions before allowing access to any resource. Consider using indirect object references and implementing consistent access control checks across all endpoints.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 NightWolf Penetration Testing installation
    Locate the NightWolf application directory or check installed packages using system package manager (e.g., 'dpkg -l', 'rpm -qa', or check program files)
    Affected if NightWolf Penetration Testing is installed on the system
  2. Determine Tracking component version
    Check the Tracking component version file, manifest, or version info within the NightWolf installation directory. Look for version 2.1.4 specifically
    Affected if The Tracking component version is 2.1.4 exactly as stated in the CVE
  3. Verify Tracking component is enabled
    Check the NightWolf configuration files (e.g., config.xml, settings.ini, or similar) for the Tracking module/component and confirm it is enabled or loaded
    Affected if The Tracking component is enabled or actively loaded in the configuration
  4. Inspect access control configuration for Tracking
    Review access control or authorization configuration files related to the Tracking component. Look for any direct object reference implementations that may lack authorization checks
    Affected if Direct object references in the Tracking component do not have proper authorization validation configured

You are affected if NightWolf Penetration Testing with Tracking component version 2.1.4 is installed and the Tracking component is enabled, and direct object references lack proper authorization validation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization validation on all object references by verifying the current user's permissions before allowing access to any resource. Consider using indirect object references and implementing consistent access control checks across all endpoints.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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