dbcve.org
Tcis 3 FirmwareOperating system · Zenitel

CVE-2025-64090

HIGH · 8.8 CVSS v3.1 Published 2026-01-09
Fix available
A fix is available. Upgrade to 9.2.3.3 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
This vulnerability allows authenticated attackers to execute commands via the hostname of the device.

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 confidence

This is a command injection vulnerability where authenticated attackers can execute arbitrary commands by providing malicious input through the device's hostname field. The vulnerability indicates that user-supplied hostname data is being passed to a system call or command interpreter without proper sanitization.

MitigationImplement strict input validation and sanitization on the hostname parameter, using allowlist approaches or parameterized commands to prevent command injection. Apply vendor patches when available.

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
Tcis 3 FirmwareOperating system
Affected:< 9.2.3.3

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 the device firmware version
    Access the Zenitel TCIS device web interface or system information page and locate the firmware version information. This is typically found under Settings, System Info, or About sections.
    Affected if The displayed firmware version is lower than 9.2.3.3
  2. Confirm web management interface is enabled
    Check if the device's web-based management interface is accessible from the network. Verify the HTTP/HTTPS service is running on the device.
    Affected if Web management interface is exposed and accessible
  3. Verify hostname configuration feature
    Navigate to the network settings or hostname configuration section in the device web interface. Confirm that the hostname field is present and can be modified.
    Affected if Hostname configuration feature is accessible and editable
  4. Check authentication status
    Review whether the device requires authentication to access the web management interface and modify settings. Determine if default credentials are in use.
    Affected if Authentication is not required or weak/default credentials are configured

You are affected if the device firmware version is below 9.2.3.3 AND the web management interface with hostname configuration is accessible, regardless of authentication status since attackers need valid credentials to exploit this vulnerability.

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 9.2.3.3 or later
Fixed in 9.2.3.3
Interim mitigation

Implement strict input validation and sanitization on the hostname parameter, using allowlist approaches or parameterized commands to prevent command injection. Apply vendor patches when available.

Recommended fix Moderate confidence

TCIS 3 Firmware version 9.2.3.3 or later

  1. 1. Identify all TCIS 3 devices in your inventory running firmware version prior to 9.2.3.3
  2. 2. Verify you have proper authentication credentials for the affected devices
  3. 3. Obtain the firmware version 9.2.3.3 or later from the official Zenitel support portal
  4. 4. Review the firmware upgrade procedure in the Zenitel documentation
  5. 5. Create a backup of the current device configuration if supported
  6. 6. Apply the firmware upgrade to each affected TCIS 3 device
  7. 7. After upgrade, verify the device is functioning correctly and the firmware version shows 9.2.3.3 or later
  8. 8. Test that the hostname configuration functionality works without command injection vulnerability
Caveat Review Zenitel release notes for any configuration or feature changes between your current version and 9.2.3.3

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

Fix this in Tcis 3 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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