A critical vulnerability in Microweber before version 1.1.20 allows unauthenticated attackers to disclose the entire users database, including admin password hashes and emails. The flaw is present in the 'controller.php' script of the users module, which can be triggered by a POST request to the /modules/ endpoint with the module parameter set to /modules/users/controller. The script outputs the users database using Laravel’s dump and die function, requiring no authentication.
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 HTML file, 'CVE-2020-13405.html', which serves as a proof-of-concept (PoC) exploit for CVE-2020-13405 affecting MicroWeber. The file provides a simple web interface where the user can input the URL of a MicroWeber module endpoint. Upon submission, the form sends a POST request to the specified endpoint with a hidden field 'module=users/controller', attempting to exploit the vulnerability. The exploit is implemented in HTML and JavaScript, and is intended for manual use by a tester or researcher. No hardcoded payloads or advanced automation are present, and the exploit does not include detection or verification logic. The main attack vector is web-based, targeting a user-supplied HTTP endpoint. The repository is a minimal, single-file PoC with clear structure and purpose.
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.