CVE-2024-8517
Spip command injection
- Published6 Sept 2024
Description
SPIP before 4.3.2, 4.2.16, and 4.1.18 is vulnerable to a command injection issue. A remote and unauthenticated attacker can execute arbitrary operating system commands by sending a crafted multipart file upload HTTP request.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2024-8517 being actively exploited?
CVE-2024-8517 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 94.6%.
How severe is CVE-2024-8517?
CVE-2024-8517 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 94.6% probability of exploitation.
Which products are affected by CVE-2024-8517?
Affected products include Spip.
How do I fix CVE-2024-8517?
Upgrade affected software to a fixed version, for example Spip 4.1.18 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2024-8517 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.