CVE-2026-115243WPvivid — Backup, Migration & Staging unrestricted file upload
CVE-2026-115243 is a unrestricted file upload in WPvivid — Backup, Migration & Staging, rated medium (6.7 on CVSS 3.1).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Deferred
What it is
Files of dangerous types can be uploaded, and the server may run or serve them.
How it is reached
An attacker can exploit it over the network, with an administrator account, and nobody has to click anything.
What an attacker gains
A successful attack can read the data it protects and change data or behaviour. In practice, this kind of flaw lets an attacker place a file the server will run or serve to others.
Is it being exploited?
There is no public report of exploitation yet. EPSS estimates a 0.31% chance of exploitation activity in the next 30 days, higher than 24% of scored CVEs.
What to do
- Upgrade WPvivid — Backup, Migration & Staging to 0.9.137 or later.
- Until it is patched, review who holds accounts that can reach it.
Description from NVD
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 this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- WordPress sites and their plugins. Plugins run inside the site with its database access, and many sites are public.
- Upload endpoints and the storage behind them. The flaw sits between uploaded content and the servers that store or serve it.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- Between uploaded content and the servers that store or serve it. An attacker who crosses it can place a file the server will run or serve to others.
Questions to answer about your own systems
- Where does WPvivid — Backup, Migration & Staging run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.