Loading vulnerability…
CVE-2020-8772 affects the InfiniteWP Client WordPress plugin before version 1.9.4.5. The vulnerability is caused by a missing authorization check in the iwp_mmb_set_request function in init.php. Due to this improper access control, an unauthenticated attacker who knows the username of a WordPress administrator can bypass normal authentication and log in as that administrator.
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: 'wp_infinitewp_auth_bypass.rb', which exploits CVE-2020-8772, an authentication bypass vulnerability in the InfiniteWP Client plugin for WordPress (versions < 1.9.4.5). The exploit targets WordPress installations with versions below 4.9 due to API changes in later versions. The module works by sending a specially crafted POST request to the InfiniteWP backend endpoint, bypassing authentication and obtaining a valid admin session cookie. It then overwrites a specified plugin file (default: index.php) with a PHP payload (default: php/meterpreter/reverse_tcp), triggers execution of the payload, and finally restores the original file contents. The exploit requires a valid administrator username and network access to the target's web interface. The code is written in Ruby and is structured as a standard Metasploit exploit module, making it weaponized and easily customizable for different payloads. The main endpoints involved are plugin file paths and the InfiniteWP backend handler.
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.
2 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.