Quick answers
- Is CVE-2026-115243 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115243 being exploited in the wild.
- How severe is CVE-2026-115243?
- Informational severity, published 4 November 2026.
- Which products and versions are affected?
- WPvivid Backup Migration & Staging 0.9.117 through 0.9.136.
- Is there a fix for CVE-2026-115243?
- 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-115243 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-115243?
- Check whether you run WPvivid Backup 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 vulnerability exists in the import upload handler which validates the file extension from one request field but saves the actual uploaded file with WordPress type-checking disabled. An authenticated administrator can exploit this mismatch to store a PHP file or other executable in the plugin's import directory, bypassing extension validation. This is a regression from the incomplete fix of CVE-2025-5961.
Affected products
- WPvivid WPvivid Backup Migration & Staging 0.9.117 through 0.9.136
Timeline
- 2026-11-02: disclosed
- 2026-11-04: advisory