CVE-2026-1618
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 · uneditedAuthentication Bypass Using an Alternate Path or Channel vulnerability in Universal Software Inc. FlexCity/Kiosk allows Privilege Escalation. 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 from Universal Software Inc. contains an authentication bypass vulnerability (CWE-287) that allows attackers to bypass normal authentication mechanisms through an alternate path or channel, enabling privilege escalation from lower-privileged to higher-privileged accounts.
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
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 and versionLocate the FlexCity/Kiosk application on the system and retrieve its version number. This is typically found in the application properties, an about dialog, or a version file within the installation directory.Affected if The installed version is Uni Yaz Flexcity and is less than 1.0.36 (versions 1.0.x through 1.0.35 are affected).
-
Verify the application is running with authentication enabledCheck the application configuration or runtime status to confirm that authentication mechanisms are currently active or configured for use.Affected if Authentication is enabled but can be bypassed through the alternate path or channel vulnerability.
-
Confirm network accessibility of the authentication interfaceDetermine if the FlexCity/Kiosk authentication interface is exposed over the network or accessible remotely rather than only locally.Affected if The authentication interface is accessible remotely, allowing external attackers to exploit the bypass.
-
Check for presence of lower-privileged user accountsReview the user accounts configured in FlexCity/Kiosk to confirm the existence of lower-privileged accounts that could be escalated to higher-privileged access.Affected if Lower-privileged accounts exist that could be elevated through the authentication bypass.
The environment is affected if Uni Yaz Flexcity version is 1.0.x where x is less than 36, authentication is enabled, and the application is accessible for remote exploitation.
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
Update FlexCity/Kiosk to version 1.0.36 or later to remediate this vulnerability. If immediate patching is not possible, implement additional access controls and monitor for unauthorized access attempts.
FlexCity/Kiosk version 1.0.36
- 1. Identify all deployed instances of FlexCity/Kiosk in your environment
- 2. Determine the current installed version of each FlexCity/Kiosk instance
- 3. For instances running version >= 1.0 and < 1.0.36, plan the upgrade to version 1.0.36
- 4. Before upgrading, perform a complete backup of the current system configuration and data
- 5. Review the release notes for version 1.0.36 to understand any specific upgrade requirements
- 6. Execute the upgrade to version 1.0.36 following the vendor's documented upgrade procedure
- 7. After upgrade, verify that the authentication mechanism is functioning correctly
- 8. Test that privilege escalation is no longer possible through alternate paths or channels
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1618 — 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-1618 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