Loading vulnerability…
CVE-2013-4557 is a remote code execution vulnerability in the SPIP Security Screen component, specifically core/securite/ecran_securite.php, before version 1.1.8. As used in SPIP 3.0.x before 3.0.12, the flaw allows remote attackers to execute arbitrary PHP code via the connect parameter. The issue is exposed through improper handling of attacker-controlled input in that parameter, resulting in PHP code execution within the context of the web application.
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.
This repository contains a single Metasploit module (spip_connect_exec.rb) that exploits a PHP code injection vulnerability (CVE-2013-4557) in the 'connect' parameter of SPIP, a popular PHP CMS. The exploit targets SPIP versions <2.0.21, <2.1.16, and <3.0.3, and allows unauthenticated remote code execution as the web server user. The module works by sending a specially crafted POST request to /spip.php with a malicious 'connect' parameter containing PHP code that decodes and executes a base64-encoded payload from the HTTP header. The exploit supports multiple platforms (Unix/Linux, Windows) and can deliver various payloads, including Meterpreter shells. The code is weaponized, as it is part of the Metasploit framework and supports customizable payloads. The repository structure is typical for a Metasploit module, with the main logic in a single Ruby file.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.