# CVE-2026-19725: WPvivid Backup & Migration < 0.9.131 - Unauthenticated Path Traversal via send_to_site_connect

> An attacker with a transfer key can create log files in arbitrary writable directories, including the web root, via path traversal.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-567f-mvhw-x8w5

## What is CVE-2026-19725?

CVE-2026-19725 is a critical path traversal vulnerability in Unknown WPvivid — Backup, Migration & Staging, published on 16 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.131 does not sanitise a value taken from an unauthenticated request before using it to build a log file path, allowing an attacker holding a site to site transfer key to create a log file in any existing writable directory of the site, including the web root.

The file name always carries a fixed suffix and the contents are always the WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.131's own log header, so only the location of the file is attacker controlled.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


## How do I fix CVE-2026-19725?

No fix has been published for CVE-2026-19725 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19725 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19725 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19725 and fix it if it is affected.

What it is: CVE-2026-19725 is a critical path traversal vulnerability in Unknown WPvivid — Backup, Migration & Staging, published on 16 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19725 exists.

Affected product: Unknown WPvivid — Backup, Migration & Staging. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19725/ (Markdown: https://insights.sbomify.com/CVE-2026-19725/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19725
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19725
- OSV: https://osv.dev/vulnerability/CVE-2026-19725

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19725/
Summaries are generated and may contain mistakes; the official description above is the record.