CVE-2024-31835: CVE-2024-31835 · Cross-site Scripting
Affects CVE-2024-31835Source CVE Database V5
Not known to be exploited · CVSS 4.7 Medium.
Data as of 26 Oct 2026, 11:07 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 64% 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:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Oct 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 |
|---|---|---|
GitHubparagbagul111/CVE-2024-31835pkg:github/paragbagul111/CVE-2024-31835Other 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
- Implement strict input validation and sanitization on the file name parameter to neutralize any potentially malicious scripts. Use well-established libraries or frameworks that automatically encode or escape user input.
- Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of XSS attacks.
- Limit user input length and restrict allowed characters for file names to minimize injection vectors.
- Monitor web application logs and user reports for suspicious activity or unexpected script execution.
- Educate users about the risks of clicking unknown or suspicious links to reduce the likelihood of user interaction exploitation.
- Regularly check for updates or patches from Flatpress CMS developers and apply them promptly once available.
- Consider deploying Web Application Firewalls (WAFs) with rules designed to detect and block XSS payloads targeting the file name parameter.
- If possible, isolate or sandbox the affected CMS instances to limit the blast radius of any successful exploit.
Description
Cross Site Scripting vulnerability in flatpress CMS Flatpress v1.3 allows a remote attacker to execute arbitrary code via a crafted payload to the file name parameter.