dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2025-3013

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 Customer Portal before 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

This is an Insecure Direct Object Reference (IDOR) vulnerability in the Customer Portal component of NightWolf Penetration Testing platform. The application fails to properly validate user authorization when accessing objects referenced by parameters in requests, allowing authenticated attackers to manipulate object identifiers to access unauthorized data or functionality.

MitigationUpgrade Customer Portal to version 2.1.4 or later. Additionally, implement proper authorization checks on all endpoints that accept object references, and use indirect object references where possible.

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. Confirm NightWolf platform installation
    Locate and identify the NightWolf Penetration Testing platform installation directory or service on the system. Check for files or services associated with NightWolf.
  2. Identify Customer Portal component version
    Locate the Customer Portal component within the NightWolf installation. Look for version information in the component's files, configuration, or metadata (e.g., version.txt, manifest, about page, or admin interface).
  3. Check Customer Portal authentication settings
    Review the Customer Portal configuration to confirm that user authentication is enabled and that the portal accepts authenticated user sessions.
  4. Identify object reference parameters in requests
    Analyze the Customer Portal web traffic or API endpoints. Look for parameters that accept object identifiers such as IDs, IDs, or references in URLs or form data.

A user is affected if the NightWolf Customer Portal component is installed and the version is below 2.1.4, with the portal accessible to authenticated users.

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

Upgrade Customer Portal to version 2.1.4 or later. Additionally, implement proper authorization checks on all endpoints that accept object references, and use indirect object references where possible.

Recommended fix Moderate confidence

Customer Portal version 2.1.4

  1. Back up the current Customer Portal installation and database before making any changes
  2. Review the NightWolf Penetration Testing Customer Portal release notes for version 2.1.4 to understand changes
  3. Obtain the version 2.1.4 release package from the official NightWolf vendor
  4. Follow the vendor's documented upgrade procedure to install version 2.1.4
  5. After upgrading, verify the IDOR vulnerability is fixed by testing access control on sensitive endpoints
  6. Ensure proper authorization checks are in place for all object references in the portal

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
23.0 hours of engineering $4,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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