Skip to main content
CVE-2026-120390VulnerabilityPublished

The WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.140 does not limit its table prefix rewrite to

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-120390· High

Not known to be exploited : upgrade to 0.9.140 soon.

Data as of 18 Nov 2026, 08:07 UTC

Severity
High

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

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
WPvivid — Backup, Migration & StagingAffected
  • <0.9.140
Fixed in
  • 0.9.140

AI-suggested

A fixed version 0.9.140 or later addresses this issue. Users should upgrade the WPvivid plugin to version 0.9.140 or newer to remediate the vulnerability.

Description

The WPvivid Backup, Migration & Staging WordPress plugin versions prior to 0.9.140 improperly handle table prefix rewriting during database backup restoration. This flaw corrupts the length of stored serialized values and enables users with Subscriber-level roles to plant PHP objects that WordPress instantiates after an administrator restores a backup.

References

Community reviews

Loading reviews…