CVE-2024-31648: n/a
Source CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% 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 15 Apr 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 2026-10-25.
What to do
AI-suggested
To mitigate this vulnerability, organizations should immediately implement strict input validation and output encoding on the Category Name parameter to prevent injection of malicious scripts. Employing a Content Security Policy (CSP) can help reduce the impact of any successful XSS attempts by restricting script execution sources. Web Application Firewalls (WAFs) should be configured to detect and block suspicious payloads targeting the vulnerable endpoint. User education on recognizing phishing attempts and suspicious links is also critical, given the requirement for user interaction. Monitoring web server logs and user activity for anomalous behavior can help detect exploitation attempts. Until an official patch is released, consider isolating or restricting access to the affected module if feasible. Finally, coordinate with the software vendor for timely updates and patches.
Description
Cross Site Scripting (XSS) in Insurance Management System v1.0, allows remote attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Category Name parameter at /core/new_category2.