CVE-2022-2863

Migration, Backup, Staging – WPvivid <= 0.9.75 - Authenticated (Administrator+) Path Traversal

2022-08-22 00:00
Rodolfo Tavares

Strategic Overview

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

At a glance

CVE-2022-2863 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.75. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality, integrity impact). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 0.9.76; sites on affected versions should update now. Disclosed August 2022, reported by Rodolfo Tavares.

Vulnerability Overview

The WPvivid backup plugin for WordPress is vulnerable to arbitrary file read due to missing parameter sanitization and validation on the 'file_name' parameter in versions up to, and including, 0.9.75. This makes it possible for authenticated attackers, with administrator level permissions and above, to access arbitrary files on the affected sites server.

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.

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

WPvivid <= 0.9.75 carries this weakness at file_name, and reaching it 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.76: builds <= 0.9.75 are affected, anything from 0.9.76 onward is not.

Remediation

Update to version 0.9.76, 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.76 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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