CVE-2026-82194

WPvivid — Backup, Migration & Staging < 0.9.134 - Authenticated (Administrator+) Arbitrary File Deletion

2026-09-02 00:00
Meher Sudhakar Abbireddi

Strategic Overview

Status
Patched in 0.9.134
Affected Plugin
WPvivid — Backup, Migration & Staging
Affected Version
< 0.9.134
CVSS
6.5Medium
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2026-82194
View all WPvivid — Backup, Migration & Staging vulnerabilities

At a glance

CVE-2026-82194 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the WPvivid WordPress plugin, affecting versions < 0.9.134. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 0.9.134; sites on affected versions should update now. Disclosed September 2026, reported by Meher Sudhakar Abbireddi.

Vulnerability Overview

The WPvivid — Backup, Migration & Staging plugin for WordPress is vulnerable to Arbitrary File Deletion due to insufficient file path validation in the [function_or_param] function in all versions up to 0.9.134. This makes it possible for authenticated attackers, with administrator-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).

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 interaction from a victim user. A successful exploit has high impact on integrity, availability.

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Reaching this weakness in WPvivid < 0.9.134 takes an account at Administrator level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.

Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For WPvivid the fix is 0.9.134: builds < 0.9.134 are affected, anything from 0.9.134 onward is not.

Remediation

Update to version 0.9.134, or a newer patched version

How does WordSec protect against this?

An attacker needs Administrator access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPvivid 0.9.134 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-82194https://www.wordfence.com/threat-intel/vulnerabilities/id/038e8775-aa53-4e45-ba4c-52ef169943abhttps://nvd.nist.gov/vuln/detail/CVE-2026-82194

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C