CVE-2026-120390 json
WPvivid Backup & Migration < 0.9.140 - Subscriber+ PHP Object Injection via Database Restore Table Name Rewrite
published 21h ago modified 8h ago also EUVD-2026-128444
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 33%
- public exploits
- 0
- none known
Summary
The WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.140 does not limit its table prefix rewrite to table names when restoring a database backup, which corrupts the length of stored serialized values and allows users with a role as low as Subscriber to plant a PHP object that WordPress instantiates after an administrator restores a backup.
Patch / fix
- Unknown WPvivid — Backup, Migration & Staging 0.9.140
Is CVE-2026-120390 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 9h ago
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-18).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/9f9851ca-3b45-4680-8eef-09f601a4e7bd/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Unknown WPvivid — Backup, Migration & Staging
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
- Technology feeds
References
-
wpscan.com
/vulnerability/9f9851ca-3b45-4680-8eef-09f601a4e7bd/
exploit, vdb-entry, technical-description
Sources
- CVE List CVE-2026-120390
- NVD CVE-2026-120390
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.