CVE-2026-2546VulnerabilityPublished 16 Feb 2026Updated 23 Feb 2026

CVE-2026-2546: LigeroSmart · Cross Site Scripting

Affects LigeroSmartSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

5.1Medium

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

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

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within 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: None: There is no impact to availability within 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 16 Feb 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

Affected software

Product	Affected	Fixed in
LigeroSmart	Affected =6.1.0 =6.1.1 =6.1.2 =6.1.3 =6.1.4 =6.1.5 =6.1.6 =6.1.7 =6.1.8 =6.1.9 =6.1.10 =6.1.11 =6.1.12 =6.1.13 =6.1.14 =6.1.15 =6.1.16 =6.1.17 =6.1.18 =6.1.19 =6.1.20 =6.1.21 =6.1.22 =6.1.23 =6.1.24 =6.1.25 =6.1.26	Fixed in–

AI-suggested

1. Implement strict input validation and output encoding on the SortBy parameter to neutralize malicious scripts. 2. Deploy a web application firewall (WAF) with rules to detect and block XSS attack patterns targeting LigeroSmart URLs. 3. Educate users to avoid clicking on suspicious or unsolicited links related to LigeroSmart interfaces. 4. Restrict access to LigeroSmart web interfaces via VPN or IP whitelisting to reduce exposure. 5. Monitor web server logs for unusual requests containing suspicious SortBy parameter values. 6. Apply Content Security Policy (CSP) headers to limit script execution sources and mitigate impact of injected scripts. 7. Regularly back up LigeroSmart data and configurations to enable recovery in case of compromise. 8. Engage with the LigeroSmart vendor or community to track patch releases and apply updates promptly once available. 9. Consider temporary disabling or restricting the vulnerable functionality if feasible until a patch is released.

Description

A security vulnerability has been detected in LigeroSmart up to 6.1.26. The affected element is an unknown function of the file /otrs/index.pl. Such manipulation of the argument SortBy leads to cross site scripting. The attack may be launched remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Impact

The primary impact of this vulnerability is on the confidentiality and integrity of users interacting with LigeroSmart instances. Successful exploitation can lead to session hijacking, allowing attackers to impersonate legitimate users and access sensitive information or perform unauthorized actions. It can also facilitate phishing attacks by injecting malicious content or redirecting users to fraudulent sites. Although availability impact is minimal, the reputational damage and potential data breaches can be significant. Organizations relying on LigeroSmart for IT service management, customer support, or internal ticketing may face operational disruptions and loss of trust. The remote and unauthenticated nature of the attack increases the risk, especially in environments with many users or exposed web interfaces. The absence of an official patch prolongs exposure, and public exploit disclosure may lead to increased attack attempts. Overall, the vulnerability poses a moderate risk but can escalate if combined with other weaknesses or social engineering.

Summary

CVE-2026-2546 identifies a cross-site scripting vulnerability in LigeroSmart, a web-based service management and ticketing system, affecting all versions up to 6.1.26. The vulnerability is located in an unspecified function within the /otrs/index.pl script, where the SortBy parameter is improperly sanitized. This flaw allows an attacker to inject malicious JavaScript code that executes in the context of the victim's browser when they interact with a crafted URL or page. The attack vector is remote and does not require authentication, but user interaction is necessary to trigger the exploit. The vulnerability can lead to theft of session cookies, redirection to malicious sites, or execution of arbitrary scripts, compromising user confidentiality and integrity. The CVSS 4.0 vector indicates low attack complexity and no privileges required, but user interaction is needed. No known exploits in the wild have been reported yet, but public disclosure raises the likelihood of exploitation attempts. The vulnerability affects a broad range of versions, making many deployments vulnerable. The lack of patch links suggests that organizations must implement interim mitigations while awaiting an official fix.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:19 UTC

Technical details

References

Community reviews

Related threats