MonsterInsights Pro 10.2.2, 10.2.0 - Unauthenticated Backdoor
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- MonsterInsights Pro
- Affected Version
10.2.0 – < 11.0.0- CVSS
- 9.8Critical
- Weakness type
- CWE-506 · Embedded Malicious Code
- CVE
CVE-2026-11976
At a glance
CVE-2026-11976 is a critical-severity Embedded Malicious Code vulnerability in the MonsterInsights Pro WordPress plugin, affecting versions 10.2.0 – < 11.0.0. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed June 2026, reported by Mike Gozdiskowski.
Vulnerability Overview
The MonsterInsights Pro plugin for WordPress contains a backdoor in versions 10.2.0 and 10.2.2. This is due to the S3 bucket getting compromised. This makes it possible for unauthenticated attackers to install and access backdoors on sites.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-506: Embedded Malicious Code
Reaching this weakness in MonsterInsights Pro 10.2.0 – < 11.0.0 takes no account at all. Embedded malicious code means functionality was deliberately placed in the software to act against the site owner's interest, rather than being an accidental defect.
Removing the software is not enough on its own — anything it created or modified while active has to be audited too. No fixed build of this plugin is recorded for MonsterInsights Pro yet, so installs running 10.2.0 – < 11.0.0 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Scanner
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in MonsterInsights Pro
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C