Loading vulnerability…
Symantec Web Gateway 5.0.x prior to 5.0.3.18 contains a remote command execution vulnerability in the management console. The issue is triggered by crafted input supplied to application scripts, allowing a remote attacker to execute arbitrary commands on the underlying system.
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 targeting a command injection vulnerability (CVE-2012-2953) in Symantec Web Gateway version 5.0.2.18. The exploit leverages a lack of input sanitization in the 'filename' parameter of the /spywall/pbcontrol.php endpoint, allowing unauthenticated remote code execution as the web server user. The module is written in Ruby and follows the standard Metasploit structure, including a check method to verify the target and an exploit method that injects arbitrary shell commands via a crafted HTTP GET request. The payload is customizable and supports generic command execution. The only relevant endpoints are /spywall/pbcontrol.php (the vulnerable endpoint) and /spywall/login.php (used for detection). The exploit does not require authentication and is operational, providing attackers with the ability to execute arbitrary commands on vulnerable systems.
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.
1 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.