CVE-2025-41084: Sesame · XSS or 'Cross-site Scripting'
Affects SesameSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% 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 20 Jan 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-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SESAME LABS S.LSesame | Affected
| Fixed in– |
AI-suggested
Organizations should immediately implement strict input validation and sanitization for SVG uploads, ideally disallowing SVG files or using a secure SVG sanitizer that removes scripts and potentially dangerous elements. Employ Content Security Policy (CSP) headers to restrict script execution and reduce the impact of any injected scripts. Limit the ability to upload logos or images to trusted users only and monitor upload endpoints for suspicious activity. Conduct regular security reviews and penetration testing focused on file upload functionalities. If possible, isolate the logo display context to prevent script execution or use sandboxed iframes. Keep the Sesame application updated and monitor SESAME LABS S.L communications for patches addressing this vulnerability. Additionally, educate users about the risks of interacting with untrusted content and implement multi-factor authentication to reduce the impact of session hijacking.
Description
Stored Cross-Site Scripting (XSS) vulnerability in Sesame web application, due to the fact that uploaded SVG images are not properly sanitized. This allows attackers to embed malicious scripts in SVG files by sending a POST request using the 'logo' parameter in '/api/v3/companies/<ID>/logo', which are then stored on the server and executed in the context of any user who accesses the compromised resource.