Loading vulnerability…
SPIP versions prior to 4.4.9 contain a blind Server-Side Request Forgery (SSRF) issue in the private area’s “syndicated sites” feature. When an authenticated user edits a syndicated site, SPIP does not validate that the provided syndication URL is a legitimate remote URL, allowing the attacker to coerce the SPIP server into issuing HTTP(S) requests to arbitrary internal or external destinations. The issue is described as blind SSRF (responses are not directly returned to the attacker) and is explicitly noted as not being mitigated by the SPIP security screen.
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.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.