A command injection vulnerability exists in op5config/welcome in system-op5config before 2.0.3, affecting op5 Monitor and op5 Appliance before 5.5.3. The vulnerability allows remote attackers to execute arbitrary commands on the system by supplying shell metacharacters in the password parameter, which are then unsafely processed by the backend.
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 (modules/exploits/multi/http/op5_welcome.rb) that exploits a remote command execution vulnerability (CVE-2012-0262) in OP5 Monitor versions 5.3.5 through 5.5.1. The exploit targets the /op5config/welcome endpoint, accessible over HTTPS (default port 443), and injects arbitrary shell commands via the password parameter in a POST request. The module supports command payloads (cmd) and can leverage Perl, Ruby, or Python for payload execution. If successful, it provides root-level command execution on the target system. The code is operational and part of the Metasploit framework, with a clear structure for detection (via timing a ping command) and exploitation. No hardcoded IPs or domains are present; the endpoint is configurable. The repository is focused and contains only the exploit module.
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.