# CVE-2026-19718: BlogVault, MalCare and WP Remote 5.16 - 6.62 - Unauthenticated Site Takeover via Connection Key Recovery

> Attackers can recover weak connection keys to gain unauthenticated administrative access to WordPress sites using affected backup and security plugins.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-63pv-w3j7-r654

## What is CVE-2026-19718?

CVE-2026-19718 is a high-severity vulnerability in Unknown BlogVault Backup & Staging, published on 26 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The BlogVault Backup & Staging WordPress plugin before 6.65, MalCare WordPress Security Plugin  WordPress plugin before 6.65, The WP Remote WordPress Plugin WordPress plugin before 6.65 do not prevent unauthenticated users from obtaining data derived from the secret that binds a site to its remote management service, and generate that secret with a weak pseudo-random number generator, allowing attackers to recover it and gain administrative access to the site.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-19718?


## How do I fix CVE-2026-19718?

No fix has been published for CVE-2026-19718 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19718 being exploited?

There is no known exploitation of CVE-2026-19718 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19718 and fix it if it is affected.

What it is: CVE-2026-19718 is a high-severity vulnerability in Unknown BlogVault Backup & Staging, published on 26 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19718 in the wild and no public exploit code.

Affected product: Unknown BlogVault Backup & Staging. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19718/ (Markdown: https://insights.sbomify.com/CVE-2026-19718/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19718
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19718
- OSV: https://osv.dev/vulnerability/CVE-2026-19718

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19718/
Summaries are generated and may contain mistakes; the official description above is the record.