dbcve.org
FlexcityApplication · Uni Yaz

CVE-2025-14349

HIGH · 8.8 CVSS v3.1 Published 2026-02-13
Fix available
A fix is available. Upgrade to 1.0.36 or later.
See remediation →
94/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
Privilege Defined With Unsafe Actions, Missing Authentication for Critical Function vulnerability in Universal Software Inc. FlexCity/Kiosk allows Accessing Functionality Not Properly Constrained by ACLs, 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 · high confidence

FlexCity/Kiosk versions prior to 1.0.36 contain a critical missing authentication vulnerability that allows unauthenticated users to access privileged functions. The application fails to properly constrain functionality by ACLs, enabling privilege escalation where lower-privileged users can perform actions reserved for higher-privilege roles.

MitigationUpgrade to FlexCity/Kiosk version 1.0.36 or later. If immediate patching is not possible, implement network-level access controls to restrict exposure of the kiosk management interface to unauthorized network segments.

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
FlexcityApplication
Affected:>= 1.0, < 1.0.36

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify FlexCity/Kiosk installed version
    Locate the FlexCity/Kiosk installation and check its version number. This may be visible in the application UI about screen, in an installer log file, in a configuration file within the installation directory, or via an API endpoint that reports version information.
    Affected if The installed version is 1.0.35 or earlier (any version >= 1.0 but < 1.0.36).
  2. Determine if management interface is network-accessible
    Identify the network endpoints or URLs used for FlexCity/Kiosk administration and determine if they are reachable from untrusted network segments. Check firewall rules, network ACLs, or VPN configurations that control access to the kiosk management ports or URLs.
    Affected if The management interface is accessible from network segments that should not have administrative access.
  3. Verify authentication is enforced on critical functions
    Test access to critical administrative functions (such as user management, system configuration, or device control endpoints) without providing valid credentials. Compare the behavior against documented authentication requirements.
    Affected if Critical functions can be accessed or invoked without proper authentication or successful login.
  4. Review ACL or access control configuration
    Examine the FlexCity/Kiosk access control list (ACL) configuration files or settings that define which users or roles can access specific functions. Verify that lower-privileged accounts cannot invoke administrative operations.
    Affected if ACLs are missing, misconfigured, or allow lower-privileged users to access restricted functionality.

You are affected if your FlexCity/Kiosk version is before 1.0.36 and the management interface or critical functions are accessible without proper authentication or access controls.

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.

dbcve · scoped
Upgrade available Upgrade to 1.0.36 or later
Fixed in 1.0.36
Interim mitigation

Upgrade to FlexCity/Kiosk version 1.0.36 or later. If immediate patching is not possible, implement network-level access controls to restrict exposure of the kiosk management interface to unauthorized network segments.

Recommended fix Moderate confidence

FlexCity/Kiosk version 1.0.36

  1. Identify all deployed instances of FlexCity/Kiosk in your environment
  2. Verify current version is below 1.0.36 by accessing the system's about or version information
  3. Obtain FlexCity/Kiosk version 1.0.36 from the official vendor (Universal Software Inc.)
  4. Test the upgrade in a non-production environment first
  5. Schedule a maintenance window for the upgrade
  6. Back up the current system configuration and any relevant data
  7. Apply the upgrade to version 1.0.36 using the vendor's documented upgrade procedure
  8. Verify the upgrade was successful by checking the new version number

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Flexcity Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14349 — 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-14349 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