Loading vulnerability…
In WikkaWiki versions 1.3.1 and 1.3.2, when the spam_logging option is enabled, the application allows remote attackers to write arbitrary PHP code to the spamlog_path file by supplying malicious content in the User-Agent HTTP header during an addcomment request. The vulnerability arises from insufficient sanitization of user-supplied input before writing to a log file.
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 (1 hidden).
This repository contains a single Metasploit module (modules/exploits/multi/http/wikka_spam_exec.rb) that exploits a remote code execution vulnerability (CVE-2011-4451) in WikkaWiki 1.3.2 r1814 when spam logging is enabled. The exploit works by logging in to the application with valid credentials, posting a comment with enough URLs to trigger spam protection, and injecting a PHP payload via the UserAgent header into the spam log file. The attacker then requests the spam log file, causing the injected PHP code to execute. The module is written in Ruby and leverages Metasploit's payload system, allowing for customizable PHP payloads. The exploit requires knowledge of a writable page and valid credentials, and targets the web application over HTTP. The structure is typical for a Metasploit exploit module, with clear separation of login, injection, and execution phases.
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.