CVE-2026-5799
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 · uneditedAuthorization bypass through User-Controlled key vulnerability in Idvlabs Software and Consulting Services Inc. Ontime allows Exploitation of Trusted Identifiers. This issue affects Ontime: through 04052026.
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 confidenceThis is an Insecure Direct Object Reference (IDOR) vulnerability where the application trusts user-controlled identifiers (such as object IDs in requests) without proper authorization validation. Attackers can manipulate these trusted identifiers to access resources belonging to other users or elevate privileges beyond what their account should permit.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Map object identifier entry pointsReview your API endpoints, URLs, and request parameters for patterns where user-supplied IDs (such as /users/123, ?id=123, or {"resource_id": 123} in request body) are used to reference data objectsAffected if your application accepts object identifiers from users without requiring authorization validation on each request
-
Verify authorization on identifier-based accessExamine the code or configuration for each endpoint that uses object IDs to confirm that an authorization check verifies the authenticated user owns or has permission to access the specific resource before returning dataAffected if any endpoint that uses object identifiers lacks explicit authorization logic that validates user permissions for that specific resource
-
Test for cross-user object accessUsing two different test accounts, attempt to access or modify a resource belonging to account A by using account A's object identifiers while authenticated as account BAffected if manipulating object identifiers from one user allows access to another user's resources
-
Check for privilege escalation pathsIdentify endpoints that modify resource ownership or permissions and verify whether user-controlled identifiers can elevate privileges beyond the authenticated user's roleAffected if object identifiers can be manipulated to gain access to administrative functions or elevated privileges
-
Review indirect reference mapsIf your application uses indirect or mapped references (such as random tokens instead of sequential IDs), verify that these mappings cannot be enumerated or predicted to access other objectsAffected if object references are predictable or enumerable rather than randomly mapped
A user is affected if their application uses object identifiers from user requests without performing explicit authorization validation for each access attempt.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper authorization checks on every API endpoint and UI action that references object identifiers. Verify that the authenticated user has explicit permission to access the requested resource before returning any data.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5799 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5799 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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