CVE-2025-41021: Sergestec SISTICK · XSS or 'Cross-site Scripting'
Affects Sergestec SISTICKSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 19% 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:N/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Oct 2025
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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Sergestec SISTICK | Affected
| Fixed in– |
AI-suggested
Since no official patches are currently available, European organizations should implement immediate compensating controls. These include: 1) Restricting access to the /admin/index.php?action=product_update endpoint to only trusted and necessary users via network segmentation and access control lists; 2) Enforcing strict authentication and session management policies, including multi-factor authentication (MFA) for all administrative users; 3) Implementing Content Security Policy (CSP) headers to limit the execution of unauthorized scripts; 4) Conducting thorough input validation and output encoding on the 'obs' parameter at the application or web server level, if possible through custom WAF (Web Application Firewall) rules; 5) Monitoring logs for unusual POST requests or suspicious activity targeting the vulnerable endpoint; 6) Educating users about the risks of clicking on untrusted links that may trigger stored XSS payloads; 7) Planning for rapid deployment of patches once Sergestec releases an official fix; 8) Regularly reviewing and updating security controls around the affected product. These steps will reduce the attack surface and limit the potential for exploitation until a permanent fix is available.
Description
Stored Cross-Site Scripting (XSS) in Sergestec's Exito v8.0, consisting of a stored XSS due to a lack of proper validation of user input by sending a POST request using the 'obs' parameter in '/admin/index.php?action=product_update'. This vulnerability could allow a remote user to send a specially crafted query to an authenticated user and steal their cookie session details.