dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-5750

HIGH · 7.6 CVSS v4.0 Published 2026-04-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/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
An insecure direct object reference (IDOR) vulnerability in the Fullstep V5 registration process allows authenticated users to access data belonging to other registered users through various vulnerable authenticated resources in the application. The vulnerable endpoints result from: '/api/suppliers/v1/suppliers//false' to list user information; and '/#/supplier-registration/supplier-registration//2' to update your user information (personal details, documents, etc.).

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

An IDOR vulnerability in Fullstep V5 allows authenticated users to access or modify other users' data through endpoints that fail to validate object references. The supplier listing endpoint '/api/suppliers/v1/suppliers//false' and registration update endpoint '/#/supplier-registration/supplier-registration//2' accept manipulated object identifiers to access arbitrary user records.

MitigationImplement proper authorization checks validating that the authenticated user owns or has permission to access the requested resource before returning or modifying any data. Additionally, validate and sanitize all object references in URLs to prevent manipulation.

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:P/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: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 Fullstep V5 installation
    Locate the Fullstep application in your environment and determine the installed version by checking application metadata, configuration files, or the product's built-in about/version page.
    Affected if Fullstep V5 is present and running
  2. Verify affected endpoint availability
    Confirm the existence and accessibility of the '/api/suppliers/v1/suppliers//false' and '/#/supplier-registration/supplier-registration//2' endpoints by attempting to access them through your application's URL structure.
    Affected if These endpoints are reachable and respond to requests
  3. Confirm authentication requirement
    Test whether these endpoints require authentication by attempting access without credentials versus with valid user credentials.
    Affected if Endpoints are accessible only when authenticated but do not enforce object-level authorization
  4. Test object reference manipulation
    Using an authenticated session, submit requests to the affected endpoints with incremented or modified object identifiers (such as changing supplier IDs) and observe if the response returns data belonging to other users.
    Affected if Manipulating object identifiers in the URL returns data from other user records
  5. Check authorization controls
    Review application logs or perform code review to determine if the endpoints validate that the authenticated user owns or has permission to access the requested resource before returning data.
    Affected if No ownership or permission validation is performed on object references

Your environment is affected if Fullstep V5 is installed, the supplier endpoints are accessible, and object identifiers can be manipulated by authenticated users to access arbitrary user records without authorization checks.

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 validating that the authenticated user owns or has permission to access the requested resource before returning or modifying any data. Additionally, validate and sanitize all object references in URLs to prevent manipulation.

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-2026-5750 — 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-2026-5750 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