The vulnerability identified as CVE-2024-8517, which affects the SPIP content management system, has been added to the VulnCheck Known Exploited Vulnerabilities (KEV) catalog. This inclusion follows reports of active exploitation, marking a significant development for a flaw that was originally disclosed and published on September 6, 2024.
According to data tracking the lifecycle of this vulnerability, there is a gap of approximately 778 days between the initial disclosure of the flaw and its recent identification as an exploited threat. The VulnCheck KEV catalog officially listed the vulnerability as exploited on October 24, 2026, with subsequent sightings reported on October 25, 2026.
While the VulnCheck catalog identifies the vulnerability as actively exploited, it is important to note that this claim currently rests on a single source. As of late October 2026, other major vulnerability trackers, including the CISA KEV catalog used by U.S. federal agencies and the European Union’s ENISA vulnerability database, do not list CVE-2024-8517 as an exploited threat. Furthermore, the Computer Incident Response Center Luxembourg (CIRCL), which acts as an aggregator for such data, has not independently corroborated the exploitation status.
The classification of CVE-2024-8517 pertains to an external control vulnerability within the SPIP framework. While the technical details regarding the specific mechanism of the flaw are documented in official CVE records, the recent reports of exploitation are based on external monitoring rather than a confirmed statement from the software developers themselves.
Public evidence of exploitation is currently limited to two reports collected by VulnCheck and mirrored by aggregators. These reports, which first surfaced on October 24, 2026, link to original sources that have not been independently verified for accuracy or scope. Consequently, while the vulnerability is now flagged in commercial threat intelligence, the extent and nature of the attacks remain unconfirmed by the vendor.
Organizations utilizing SPIP are advised to monitor official security bulletins from the project maintainers for any specific remediation guidance or patches. Given the discrepancy between commercial threat intelligence and government-backed vulnerability catalogs, security teams should prioritize standard patching protocols while evaluating the risk posed by this specific CVE within their own infrastructure.
The timeline of 778 days between disclosure and reported exploitation highlights the persistent risk posed by older, unpatched vulnerabilities. Even when a flaw is not widely publicized as exploited immediately upon discovery, the potential for it to be integrated into malicious campaigns remains a concern for administrators of web-based content management systems.
As of the current reporting period, there is no official confirmation from the SPIP project regarding the specific exploitation campaigns mentioned in the VulnCheck data. Users should rely on official project channels for authoritative information regarding the security posture of their installations.





