CVE-2026-82193

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

2026-09-02 00:00
reconnaissance

Strategic Overview

Status
Patched in 0.9.134
Affected Version
< 0.9.134
CVSS
7.2High
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2026-82193
View all WPvivid — Backup, Migration & Staging vulnerabilities

At a glance

CVE-2026-82193 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the WPvivid WordPress plugin, affecting versions < 0.9.134. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, 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 reconnaissance.

Vulnerability Overview

The WPvivid — Backup, Migration & Staging plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to 0.9.134. This is due to missing file type validation. This makes it possible for authenticated attackers, with administrator-level access and above, to upload arbitrary files on the affected site's server, which may make remote code execution possible.

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 confidentiality, integrity, availability — full site compromise territory.

CWE-434: Unrestricted Upload of File with Dangerous Type

Reaching this weakness in WPvivid < 0.9.134 takes an account at Administrator level or above. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. 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. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created 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
  • Scanner
  • Alerts

External References

Related records

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