CVE-2026-19718

The WP Remote WordPress Plugin, Malcare Security, and BlogVault Backup & Staging < 6.65 - Unauthenticated Site Takeover via Brute Force

2026-08-24 00:00
Jakub Herman

Strategic Overview

Status
Patched in 6.65
Affected Version
< 6.65
CVSS
9.8Critical
Weakness type
CWE-338 · Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
CVE
CVE-2026-19718
View all MalCare WordPress Security Plugin – Malware Scanner, Cleaner, Security Firewall vulnerabilities

At a glance

CVE-2026-19718 is a critical-severity Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) vulnerability in the MalCare WordPress Security Plugin WordPress plugin, affecting versions < 6.65. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 6.65; sites on affected versions should update now. Disclosed August 2026, reported by Jakub Herman.

Vulnerability Overview

Multiple plugins for WordPress are vulnerable to unauthenticated site takeover in various versions. This is due to a weak pseudo-random number generator that makes it possible for attackers to brute force and connect to the remote connection feature. This makes it possible for unauthenticated attackers to connect a site to their remote management software and take it over.

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-338: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)

The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong.

Remediation

Update to version 6.65, or a newer patched version

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. None of that substitutes for the fix: MalCare WordPress Security Plugin 6.65 closes this, and updating the plugin is the step that ends it.

  • 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