Loading vulnerability…
The vulnerability exists in the PageListSort function within scripts/pagelist.php in PmWiki versions prior to 2.2.35. It allows remote attackers to execute arbitrary PHP code by injecting PHP sequences into the 'order' parameter of a pagelist directive. The vulnerability is due to improper sanitization of user-supplied input, which is passed to PHP's create_function, enabling code execution.
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/pmwiki_pagelist.rb) that exploits a remote PHP code injection vulnerability in PmWiki versions 2.0.0 to 2.2.34 (CVE-2011-4453). The exploit targets the pagelist.php script, allowing an attacker to execute arbitrary PHP code on the server via specially crafted HTTP POST requests. The module first checks if the target is running a vulnerable version by requesting the PmWiki version page. For exploitation, it injects a PHP payload (base64-encoded) through a custom HTTP header, which is then executed on the server using eval(base64_decode(...)). The exploit is weaponized, as it is part of the Metasploit framework and allows for customizable payloads. The only file in the repository is a Ruby script implementing the exploit logic, and it requires the attacker to specify the URI path to the PmWiki installation. The main attack vector is network-based, leveraging HTTP requests to the vulnerable endpoint.
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.