Loading vulnerability…
In XAMPP for Windows versions before 7.2.29, 7.3.x before 7.3.16, and 7.4.x before 7.4.4, an unprivileged user can modify the xampp-control.ini file. This file controls configuration for .exe files executed by the XAMPP Control Panel. By altering this configuration, the attacker can cause the Control Panel to execute arbitrary commands with the privileges of any user who subsequently runs the Control Panel, including administrators.
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 (3 hidden).
Repository contains a minimal PowerShell proof-of-concept for CVE-2020-11107 (XAMPP Control Panel on Windows). The exploit is a local privilege escalation technique that abuses insecure permissions on the global configuration file C:\xampp\xampp-control.ini. The script (50337.ps1) reads the third line of the INI file, extracts the value after '=', and replaces that value everywhere in the file with an attacker-supplied executable path (hardcoded as C:\temp\msf.exe). When a higher-privileged user later runs C:\xampp\xampp-control.exe and opens logs (which invokes the configured editor), the attacker’s binary executes with the victim’s privileges. README.md documents affected versions (XAMPP <7.2.29, 7.3.x<7.3.16, 7.4.x<7.4.4), setup/trigger steps, and an example reverse-shell payload generated via msfvenom and caught with netcat. No network scanning or remote exploitation is implemented; the only code is the local config overwrite PoC.
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.