CVE-2026-1619
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 Universal Software Inc. FlexCity/Kiosk allows Exploitation of Trusted Identifiers. This issue affects FlexCity/Kiosk: from 1.0 before 1.0.36.
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 confidenceThe FlexCity/Kiosk application contains an IDOR (Insecure Direct Object Reference) vulnerability where user-controlled keys are not properly validated during authorization checks, allowing attackers to manipulate trusted identifiers to access unauthorized resources or functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.0, < 1.0.36CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
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.
-
Identify FlexCity/Kiosk installation versionLocate the version file, about page, or admin interface that displays the current FlexCity/Kiosk application version. Check application metadata or deployment documentation if direct access is unavailable.Affected if The installed version is Uni Yaz Flexcity version 1.0 or higher but lower than 1.0.36
-
Verify if user-supplied identifiers control access to resourcesReview application source code, configuration, or API endpoints to determine whether authorization checks rely on identifiers (such as IDs, keys, or references) that originate from user input rather than from trusted internal sources.Affected if User-supplied identifiers are directly used in authorization decisions without validation against the authenticated user's permissions
-
Inspect authorization logic for missing validationExamine the authorization module or middleware that handles resource access control. Look for patterns where object references (keys, IDs) passed in requests are trusted without verifying the requesting user has rights to that specific object.Affected if The authorization logic does not validate that the authenticated user owns or has permission to access the resource identified by the user-supplied key
-
Check application logs for anomalous access patternsReview access logs, audit trails, or security event logs for requests that manipulate identifier parameters (such as sequential IDs, UUIDs, or record keys) across different user contexts, which may indicate exploitation attempts.Affected if Logs show access attempts using manipulated identifiers that deviate from expected user resource boundaries
You are affected if the FlexCity/Kiosk version is 1.0 or higher but below 1.0.36 AND the application uses user-supplied identifiers in its authorization logic without proper validation.
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.
dbcve · scoped1.0.36
Upgrade to FlexCity/KiosK version 1.0.36 or later; implement proper authorization validation that does not rely on user-supplied identifiers for access decisions.
FlexCity/Kiosk version 1.0.36
- Upgrade FlexCity/Kiosk from the current version (>=1.0 and <1.0.36) to version 1.0.36 or later
- After upgrading, verify the installed version is 1.0.36 or higher to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1619 — 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-1619 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