CVE-2024-33424: cmsimple · A Cross-site Scripting (XSS)
Affects cmsimpleSource CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% 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 1 May 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubadiapera/cmsimplepkg:github/adiapera/cmsimpleOther 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
To mitigate CVE-2024-33424, organizations should implement the following specific measures: 1) Immediately audit and sanitize all user inputs in the Downloads parameter within the Language section of CMSimple, applying strict input validation and output encoding to neutralize malicious scripts. 2) Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of potential XSS payloads. 3) Limit user privileges and restrict access to the Settings menu to trusted administrators only, minimizing exposure. 4) Monitor web server logs and application behavior for unusual requests or payloads targeting the Downloads parameter. 5) Educate users and administrators about the risks of clicking untrusted links or opening suspicious content. 6) Regularly check for official patches or updates from CMSimple developers and apply them promptly once available. 7) Consider deploying web application firewalls (WAFs) with custom rules to detect and block XSS attack patterns targeting this vulnerability. These steps go beyond generic advice by focusing on the specific vulnerable parameter and CMS context.
Description
A cross-site scripting (XSS) vulnerability in the Settings menu of CMSimple v5.15 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Downloads parameter under the Language section.