CVE-2026-1049: LigeroSmart · Cross-site Scripting
Affects LigeroSmartSource CVE Database V5
Public exploit available · CVSS 5.1 Medium.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% 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:PExploitation evidence
Disclosed: evidence found.
CVE published 17 Jan 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LigeroSmart | Affected
| Fixed in– |
GitHubligerosmart/ligerosmartpkg:github/ligerosmart/ligerosmartOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until an official patch is released, organizations should implement strict input validation and output encoding on the TicketID parameter to neutralize malicious scripts. Web application firewalls (WAFs) can be configured to detect and block suspicious payloads targeting the /otrs/index.pl endpoint. Administrators should educate users about the risks of clicking untrusted links and consider disabling or restricting access to vulnerable endpoints if feasible. Monitoring web server logs for unusual requests to /otrs/index.pl with suspicious TicketID values can help detect attempted exploitation. Employing Content Security Policy (CSP) headers can mitigate the impact of XSS by restricting script execution sources. Regular backups and incident response plans should be updated to address potential compromise scenarios. Organizations should track LigeroSmart updates closely and apply patches immediately upon release. If possible, isolating the LigeroSmart instance behind VPN or internal networks can reduce exposure to external attackers.
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 TicketID leads to cross site scripting. It is possible to launch the attack 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.
References
- vuldb.com (opens in a new tab)
- vuldb.com (opens in a new tab)
- vuldb.com (opens in a new tab)
- vuldb.com (opens in a new tab)
- github.com/LigeroSmart/ligerosmart/issues/280 (opens in a new tab)
- github.com/LigeroSmart/ligerosmart/issues/280 (opens in a new tab)
- github.com/LigeroSmart/ligerosmart/ (opens in a new tab)