CVE-2024-48535: esoft_planner_cve · A Stored Cross-site Scripting (XSS)
Affects esoft_planner_cveSource CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 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 |
|---|---|---|
GitHubesoft-planner-cve/esoft_planner_cvepkg:github/esoft-planner-cve/esoft_planner_cveOther 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-48535, organizations should implement strict input validation on the Name parameter to reject or sanitize any HTML or script content before storage. Employing context-aware output encoding when rendering user-supplied data in web pages is critical to prevent script execution. Deploying a robust Content Security Policy (CSP) can further restrict the execution of unauthorized scripts. Access controls should be reviewed to minimize the number of users who can submit data that is stored and displayed to others. Regular security audits and code reviews focusing on input handling can identify similar issues proactively. Monitoring web application logs for unusual input patterns or error messages may help detect attempted exploitation. Until an official patch is released, consider applying virtual patching via web application firewalls (WAFs) configured to detect and block XSS payloads targeting the Name parameter. User awareness training about phishing and suspicious links can reduce the risk of triggering malicious scripts. Finally, maintain an incident response plan to quickly address any detected exploitation attempts.
Description
A stored cross-site scripting (XSS) vulnerability in eSoft Planner 3.24.08271-USA allows attackers to execute arbitrary web scripts or HTML via injecting a crafted payload into the Name parameter.