Loading vulnerability…
Apache Struts 2 (before 2.3.14.2) contains an OGNL code injection flaw in the handling of the includeParams attribute for the URL (s:url) and A (s:a) tags. A crafted request can cause Struts to improperly re-evaluate attacker-controlled request parameters as OGNL expressions when includeParams is used, resulting in arbitrary OGNL evaluation. This issue is described as an incomplete fix for CVE-2013-1966.
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 (struts_include_params.rb) that exploits a remote code execution vulnerability in Apache Struts versions prior to 2.3.14.2 (CVE-2013-2115, CVE-2013-1966). The exploit leverages a flaw in the way Struts handles request parameters, allowing attackers to inject arbitrary OGNL expressions and bypass security restrictions. The module is highly weaponized, supporting payload upload and execution for Windows, Linux, and Java platforms. It allows the attacker to specify the HTTP method (GET or POST), the vulnerable parameter, and the target URI. The default endpoint is '/struts2-blank/example/HelloWorld.action', but this can be changed to match the target application. The exploit uploads a payload (such as a reverse shell or meterpreter) and executes it, granting the attacker remote code execution on the target server. The code is structured as a typical Metasploit module, with options for configuration, payload generation, and cleanup. No hardcoded IP addresses or domains are present, but the module targets HTTP endpoints on the victim server.
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.