Loading vulnerability…
A cross-site scripting (XSS) vulnerability exists in SPIP versions prior to 4.1.14 and 4.2.x prior to 4.2.8, where the name of an uploaded file is not properly sanitized. This allows an attacker to inject malicious JavaScript code via the filename, which is then executed in the context of the application. The issue is related to the handling of filenames in javascript/bigup.js and javascript/bigup.utils.js.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Small standalone repository containing one Python exploit (`cve.py`) and a README. The script is a Python 3 unauthenticated RCE exploit/helper for SPIP BigUp. It first probes likely SPIP pages to scrape the hidden form fields `formulaire_action` and `formulaire_action_args`, then sends a crafted multipart/form-data POST to the supplied base URL. The exploit embeds PHP code inside a multipart field name so that the vulnerable BigUp processing path executes `shell_exec(base64_decode(...))`. Output is exfiltrated in the HTTP response header `X-Command-Output`, which the script decodes and prints. Operationally, it supports vulnerability checking via `whoami`, one-shot command execution with `-c`, and an interactive shell loop. The repository appears genuine and functional, not merely a detector, though there is a naming inconsistency between the repository/README mention of CVE-2024-23659 and the script’s internal reference to CVE-2024-8517.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.