CVE-2024-23659: SPIP · Cross-site Scripting
Source CVE Database V5
Not known to be exploited · CVSS 6.1 Medium : upgrade to 4.2.8 or 4.1.14 when convenient.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.2.8, 4.1.14
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 19 Jan 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
Upgrade spip/bigup to 4.2.8 or 4.1.14.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubspip/biguppkg:github/spip/bigupOther 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
European organizations should immediately verify their SPIP version and upgrade to at least 4.1.14 or 4.2.8 where this vulnerability is addressed. If upgrading is not immediately possible, organizations should implement strict input validation and sanitization on file upload names, ensuring that any special characters or scripts are neutralized before processing or rendering. Web application firewalls (WAFs) can be configured to detect and block suspicious payloads in file names or HTTP requests targeting the vulnerable endpoints (javascript/bigup.js and javascript/bigup.utils.js). Additionally, organizations should enforce Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in the browser context, mitigating the impact of potential XSS payloads. User awareness training to recognize phishing attempts that could trigger the vulnerability is also recommended. Regular security audits and penetration testing focused on web application vulnerabilities should be conducted to detect any residual or related issues. Finally, monitoring web logs for unusual file upload patterns or script injection attempts can provide early warning of exploitation attempts.
Description
SPIP before 4.1.14 and 4.2.x before 4.2.8 allows XSS via the name of an uploaded file. This is related to javascript/bigup.js and javascript/bigup.utils.js.
References
- blog.spip.net/Mise-a-jour-de-maintenance-et-securite-sortie-de-SPIP-4-2-8-SPIP-4-1-14.html?lang=fr (opens in a new tab)
- git.spip.net/spip/bigup/commit/ada821c076d67d1147a195178223d0b4a6d8cecc (opens in a new tab)
- git.spip.net/spip/bigup/commit/0757f015717cb72b84dba0e9a375ec71caddf1c2 (opens in a new tab)