CVE-2024-41613: Symphony CMS · A Cross Site Scripting (XSS)
Source CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2024
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
AI-suggested
To mitigate CVE-2024-41613, organizations should implement strict input validation and output encoding on all user-supplied content, particularly in the note editing functionality of Symphony CMS. Employing Content Security Policy (CSP) headers can help restrict the execution of unauthorized scripts. Until an official patch is released, consider disabling or restricting note editing capabilities to trusted users only. Regularly monitor web application logs for suspicious input patterns indicative of XSS attempts. Employ web application firewalls (WAFs) with rules designed to detect and block XSS payloads targeting Symphony CMS. Educate users about the risks of interacting with untrusted content and encourage the use of updated browsers with built-in XSS protections. Finally, maintain an incident response plan to quickly address any exploitation attempts.
Description
A Cross Site Scripting (XSS) vulnerability in Symphony CMS 2.7.10 allows remote attackers to inject arbitrary web script or HTML by editing note.