dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2025-13829

HIGH · 8.6 CVSS v4.0 Published 2025-12-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/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
Incorrect Authorization vulnerability in Data Illusion Zumbrunn NGSurvey allows any logged-in user to obtain the private information of any other user. Critical information retrieved: * APIKEY (1 year user Session) * RefreshToken (10 minutes user Session) * Password hashed with bcrypt * User IP * Email * Full Name

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

NGSurvey contains an Incorrect Authorization vulnerability where the application fails to properly validate user permissions when accessing user data endpoints. Any authenticated user can retrieve sensitive information (API keys, refresh tokens, bcrypt password hashes, IP addresses, emails, full names) of any other user in the system by manipulating request parameters to access unauthorized resources.

MitigationImplement proper authorization checks on all user data endpoints to ensure users can only access their own data. Validate the authenticated user's identity against the requested resource and enforce strict access controls.

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/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:Y/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 NGSurvey installation
    Identify if NGSurvey is deployed in your environment by checking for the application codebase, web server logs, or service documentation mentioning 'NGSurvey'. Look for directories named 'NGSurvey' or files containing 'NGSurvey' in your web root or application directories.
    Affected if NGSurvey is installed and running in your environment
  2. Identify user data endpoints
    Review the application's API documentation, or use web proxy tools to map the application's endpoints. Look for endpoints that handle user-related data such as '/api/users', '/api/user/profile', '/api/user/data', or similar paths that accept user identifiers as parameters.
    Affected if The application exposes endpoints that accept user IDs or identifiers as parameters
  3. Verify authentication is required
    Attempt to access identified user data endpoints without providing any authentication credentials. Observe whether the application returns an authentication error or redirects to a login page.
    Affected if The endpoints require authentication but do not enforce proper authorization checks
  4. Test for horizontal privilege escalation
    Log in to the application with a regular user account. Using a web proxy or API testing tool, modify request parameters (such as user ID, user identifier, or resource ID) to target a different user's data. For example, if your user ID is 5, try changing the parameter to access user ID 1, 2, or any other ID. Observe whether the application returns sensitive data belonging to other users.
    Affected if An authenticated user can retrieve, view, or modify another user's data by manipulating request parameters

If NGSurvey is running and user data endpoints allow any authenticated user to access or modify another user's data by simply changing an ID or parameter in the request, your environment is affected by this vulnerability.

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 checks on all user data endpoints to ensure users can only access their own data. Validate the authenticated user's identity against the requested resource and enforce strict access controls.

Have this fixed 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 help mitigating

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-13829 — 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-13829 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