CVE-2024-48707: Collabtive_StoredXSS · Cross-site Scripting
Affects Collabtive_StoredXSSSource CVE Database V5
Not known to be exploited · CVSS 5.4 Medium.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% 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 22 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 |
|---|---|---|
GitHubanoncoder01/Collabtive_StoredXSSpkg:github/anoncoder01/Collabtive_StoredXSSOther 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-48707, organizations should first monitor official Collabtive channels for patches or updates addressing this vulnerability. In the absence of patches, apply the following specific mitigations: 1) Implement strict input validation and output encoding for the 'name' parameter in managemilestone.php and admin.php to neutralize malicious scripts. 2) Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious payloads targeting these parameters and actions. 3) Enforce the principle of least privilege by limiting user permissions to reduce the number of users who can trigger the vulnerable actions. 4) Educate users about phishing and social engineering risks to reduce the likelihood of successful exploitation requiring user interaction. 5) Conduct regular security audits and penetration testing focusing on XSS vectors within Collabtive. 6) Consider isolating Collabtive instances behind VPNs or internal networks to reduce exposure to external attackers. 7) Enable Content Security Policy (CSP) headers to restrict script execution sources, mitigating the impact of injected scripts.
Description
Collabtive 3.1 is vulnerable to Cross-site scripting (XSS) via the name parameter under (a) action=add or action=edit within managemilestone.php file and (b) action=addpro within admin.php file.