VulnerabilityPublished 17 Feb 2026Updated 6 Mar 2026

CVE-2026-2620: Huace Monitoring and Early Warning System · SQL Injection

Affects Huace Monitoring and Early Warning SystemSource CVE Database V5

Public exploit available · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score

6.9Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

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 or the CVSS exploit maturity 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

Affected software

Product	Affected	Fixed in
HuaceMonitoring and Early Warning System	Affected =2.2	Fixed in–

AI-suggested

Given the lack of an official patch from the vendor, organizations should implement immediate compensating controls. These include deploying web application firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the /Web/SysManage/ProjectRole.aspx endpoint and the 'ID' parameter. Input validation and sanitization should be enforced at the application level if source code access is available. Network segmentation can limit exposure of the vulnerable system to untrusted networks. Regular monitoring of logs for suspicious SQL query patterns or unexpected database errors is essential. Organizations should also consider restricting access to the affected endpoint through IP whitelisting or VPN-only access. Finally, maintain up-to-date backups of critical data to enable recovery in case of data manipulation or deletion.

Description

A weakness has been identified in Huace Monitoring and Early Warning System 2.2. Affected by this issue is some unknown functionality of the file /Web/SysManage/ProjectRole.aspx. Executing a manipulation of the argument ID can lead to sql injection. It is possible to launch the attack remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The exploitation of CVE-2026-2620 could have significant consequences for organizations relying on the Huace Monitoring and Early Warning System. Attackers could gain unauthorized access to sensitive monitoring data, alter or delete critical information, or escalate further attacks within the network. This could undermine the reliability and trustworthiness of early warning operations, potentially delaying responses to critical events. Data confidentiality breaches could expose sensitive operational details, while integrity violations might lead to false alerts or missed warnings. Although availability impact is limited, the overall disruption to monitoring functions could have cascading effects on organizational security and safety. The presence of a public exploit increases the likelihood of opportunistic attacks, especially against unpatched systems.

Summary

CVE-2026-2620 is a SQL injection vulnerability identified in Huace Monitoring and Early Warning System version 2.2. The flaw exists in the handling of the 'ID' parameter within the /Web/SysManage/ProjectRole.aspx endpoint, where insufficient input validation allows an attacker to inject malicious SQL code. This injection can be performed remotely without any authentication or user interaction, making exploitation relatively straightforward. The vulnerability enables attackers to manipulate backend SQL queries, potentially leading to unauthorized data retrieval, modification, or deletion. The CVSS 4.0 score of 6.9 reflects a medium severity, considering the network attack vector, lack of required privileges, and absence of user interaction, but limited impact on system availability and scope. The vulnerability primarily threatens the confidentiality and integrity of the data managed by the system, which is critical for monitoring and early warning operations.

References

Community reviews

Loading reviews…