CVE-2025-64092VulnerabilityPublished 9 Jan 2026

CVE-2025-64092: Zenitel ICX500 · SQL Injection

Affects Zenitel ICX500Source CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 1.4.3.3 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.4.3.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade ICX500 and ICX510 to 1.4.3.3.

Affected software

Product	Affected	Fixed in
ZenitelICX500	Affected <1.4.3.3	Fixed in 1.4.3.3
ZenitelICX510	Affected <1.4.3.3	Fixed in 1.4.3.3

AI-suggested

1. Immediately inventory all Zenitel ICX500 devices and verify their firmware versions. Prioritize upgrading all devices to version 1.4.3.3 or later once the patch is officially released by Zenitel. 2. If you cannot patch yet, restrict network access to ICX500 management interfaces by implementing strict firewall rules limiting access to trusted IP addresses and internal networks only. 3. Employ network segmentation to isolate ICX500 devices from public or less secure network zones, reducing exposure to potential attackers. 4. Monitor network traffic for unusual GET requests targeting ICX500 devices, which may indicate exploitation attempts. 5. Disable any unnecessary web services or interfaces on the ICX500 devices to minimize attack surface. 6. Conduct regular vulnerability scans and penetration tests focusing on ICX500 devices to detect potential exploitation. 7. Educate IT and security teams about this vulnerability and ensure incident response plans include steps for potential data breaches involving these devices. 8. Engage with Zenitel support channels to obtain official patches and security advisories promptly. 9. Consider deploying Web Application Firewalls (WAF) or Intrusion Prevention Systems (IPS) with rules to detect and block SQL injection patterns targeting ICX500 devices. 10. Review and enforce strong access control policies and logging on ICX500 devices to detect unauthorized access attempts.

Description

This vulnerability allows unauthenticated attackers to inject an SQL request into GET request parameters and directly query the underlying database.

Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality of sensitive communication data managed by Zenitel ICX500 devices. Unauthorized database queries could expose user credentials, call records, and configuration settings, potentially enabling further attacks or espionage. Critical infrastructure sectors such as transportation, public safety, and industrial facilities that rely on ICX500 for secure communication are particularly vulnerable. Data leakage could lead to privacy violations, regulatory non-compliance (e.g., GDPR), and reputational damage. Although the vulnerability does not directly impact system integrity or availability, the exposure of sensitive information could facilitate subsequent attacks or unauthorized access. The ease of exploitation without authentication increases the threat level, especially in environments where these devices are accessible from untrusted networks or the internet. European organizations with inadequate network segmentation or remote access controls face heightened risk. The lack of known exploits in the wild suggests a window for proactive mitigation before widespread exploitation occurs.

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

zenitel.com/sites/default/files/2025-12/A100K12333%20Zenitel%20Security%20Advisory.pdf (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jan 2026, 10:32 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats