The WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.140 does not prevent serialized data it cannot
Source GCVE Database
Not known to be exploited : upgrade to 0.9.140 soon.
Data as of 18 Nov 2026, 08:07 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 0.9.140
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade WPvivid (WordPress plugin) to 0.9.140.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WPvivid — Backup, Migration & Staging | Affected
| Fixed in
|
AI-suggested
Upgrade the WPvivid Backup, Migration & Staging plugin to version 0.9.140 or later where this vulnerability is fixed. No other mitigation or workaround is provided in the available data. Administrators should apply the update before restoring backups to prevent exploitation.
Description
The WPvivid Backup, Migration & Staging WordPress plugin versions before 0.9.140 have a vulnerability where serialized data that cannot be safely unserialized is re-serialized as a PHP object during site migration. This flaw allows users with the Subscriber role to plant a PHP object that gets instantiated by WordPress after an administrator restores a backup on a different URL.