CVE-2026-19725

WPvivid — Backup, Migration & Staging < 0.9.131 - Unauthenticated Path Traversal

2026-08-20 00:00
Nir Yehoshua

Strategic Overview

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

At a glance

CVE-2026-19725 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the WPvivid WordPress plugin, affecting versions < 0.9.131. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 0.9.131; sites on affected versions should update now. Disclosed August 2026, reported by Nir Yehoshua.

Vulnerability Overview

The WPvivid — Backup, Migration & Staging plugin for WordPress is vulnerable to Path Traversal in all versions up to 0.9.131. This is due to insufficient validation of a user supplied path. This makes it possible for unauthenticated attackers to access files and directories outside of the intended directory.

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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

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

Reaching this weakness in WPvivid < 0.9.131 takes no account at all. 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.131: builds < 0.9.131 are affected, anything from 0.9.131 onward is not.

Remediation

Update to version 0.9.131, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPvivid 0.9.131 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-19725https://www.wordfence.com/threat-intel/vulnerabilities/id/f3f1e629-fe60-4793-b9f1-c02a7a2542aahttps://nvd.nist.gov/vuln/detail/CVE-2026-19725

Related records

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