Skip to main content
CVE-2026-1049VulnerabilityPublished Updated

CVE-2026-1049: LigeroSmart · Cross Site Scripting

Affects LigeroSmartSource CVE Database V5

0

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 06:26 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 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:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
LigeroSmartAffected
  • =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–
GitHubligerosmart/ligerosmartpkg:github/ligerosmart/ligerosmartOther threatsAffected
  • =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–

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

Community reviews

Loading reviews…