Quick answers
- Is CVE-2026-115242 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115242 being exploited in the wild.
- How severe is CVE-2026-115242?
- Informational severity, published 4 November 2026.
- Which products and versions are affected?
- WPvivid Backup, Migration & Staging before 0.9.137.
- Is there a fix for CVE-2026-115242?
- Yes: fixed in 0.9.137. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115242 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-115242?
- Check whether you run WPvivid Backup or Migration & Staging at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.9.137
Technical details
The staging-start handler does not properly sanitize the staging destination folder path, applying only a generic text filter instead of the correct filename sanitizer used by the writability-check handler. An authenticated administrator can supply a path containing directory traversal sequences to write plugin output outside the WordPress installation directory via path traversal (CWE-22).
Affected products
- WPvivid Backup Migration & Staging before 0.9.137
Timeline
- 2026-11-02: disclosed
- 2026-11-04: advisory