sales@hackhalt.com

Home / Threats / CVE-2026-120391

WPvivid - Security Vulnerability (CVE-2026-120391)

CVE-2026-120391

The WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.140 does not prevent serialized data it cannot safely unserialize from being re-serialized as a PHP object during a site migration, allowing users with a role as low as Subscriber to plant a PHP object that WordPress instantiates after an administrator restores a backup onto a different URL.

CVE-2026-120391

HIGH CVSS 7.1 Published 2026-11-18 Updated 2026-11-19
AI Risk Elevated (65/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P3 Priority
Severity Band HIGH
CVSS Vector CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
Affected Components 1
Reference Links 1
AI Risk Engine Elevated (65/100)
Exploitability Medium
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-11-18 CVE published and first recorded in the threat feed.
  2. 2026-11-19 Record updated with latest vulnerability metadata.
  3. 2026-11-20 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 1 day ago

AI enriched 1 day ago (2026-11-20 18:13 UTC)

Technical Summary

The WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.140 does not prevent serialized data it cannot safely unserialize from being re-serialized as a PHP object during a site migration, allowing users with a role as low as Subscriber to plant a PHP object that WordPress instantiates after an administrator restores a backup onto a different URL.

Potential Impact

Severity is HIGH (CVSS 7.1). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Medium based on severity and technical exposure profile.

Primary risk drivers: severity and technical exposure profile

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 65/100 (Elevated, Medium) with priority P3 Priority. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

WPvivid PLUGIN · wpvivid Affected: < 0.9.140 Fixed in: 0.9.140

References

What to do about this

Patch promptly The consequence is significant even where an attacker needs a foothold first.

Fix it

Update WPvivid to 0.9.140 or later.

That is the complete fix. Everything below is what protects you in the meantime.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs WPvivid, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs WPvivid. Versions below 0.9.140 are vulnerable; that release and later are not.

How do I fix it?

Update WPvivid to version 0.9.140 or later. That is the complete fix. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

What can an attacker actually do?

This is a PHP Object Injection flaw. An attacker who exploits it can construct objects the application never intended, often reaching code execution.