MalCare WordPress Security Plugin – Malware Scanner, Cleaner, Security Firewall <= 6.69 - Unauthenticated Denial of Service
Strategic Overview
- Status
- Patched in 6.72
- Affected Version
<= 6.69- CVSS
- 7.5High
- Weakness type
- CWE-400 · Uncontrolled Resource Consumption
- CVE
CVE-2026-84776
At a glance
CVE-2026-84776 is a high-severity Uncontrolled Resource Consumption vulnerability in the MalCare WordPress Security Plugin WordPress plugin, affecting versions <= 6.69. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high availability impact). Exploitation requires no authentication. The issue is fixed in version 6.72; sites on affected versions should update now. Disclosed September 2026, reported by Ananda Dhakal.
Vulnerability Overview
The MalCare WordPress Security Plugin – Malware Scanner, Cleaner, Security Firewall plugin for WordPress is vulnerable to Denial of Service in all versions up to, and including, 6.69. This is due to insufficient validation of user supplied input. This makes it possible for unauthenticated attackers to make the affected site unavailable.
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 availability.
CWE-400: Uncontrolled Resource Consumption
Reaching this weakness in MalCare WordPress Security Plugin <= 6.69 takes no account at all. Uncontrolled resource consumption means a request can make the server do an amount of work it never bounds, because the size or repetition of the job is taken from the request rather than capped by the code.
A single caller can hold PHP workers, database connections or disk open long enough to slow the site for everyone, without needing any account or any other flaw. For MalCare WordPress Security Plugin the fix is 6.72: builds <= 6.69 are affected, anything from 6.72 onward is not.
Remediation
Update to version 6.72, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: MalCare WordPress Security Plugin 6.72 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in MalCare WordPress Security Plugin – Malware Scanner, Cleaner, Security Firewall
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C