Skip to main content
VulnerabilityPublished

CVE-2026-121151: UpdraftPlus: WP Backup & Migration Plugin · Deserialization of Untrusted Data

Affects UpdraftPlus: WP Backup & Migration PluginSource CVE Database V5

0
Compare

Not known to be exploited : upgrade to 2.26.16.26 soon.

Data as of 21 Nov 2026, 06:27 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 2.26.16.26, 1.26.16

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 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 20 Nov 2026.

What to do

Upgrade UpdraftPlus: WP Backup & Migration to 2.26.16.26 (Plugin) or 1.26.16 (Plugin).

Affected software

ProductAffectedFixed in
UpdraftPlus: WP Backup & Migration PluginAffected
  • >=2.0.0 <2.26.16.26
Fixed in
  • 2.26.16.26
UpdraftPlus: WP Backup & Migration PluginAffected
  • <1.26.16
Fixed in
  • 1.26.16

AI-suggested

Upgrade the UpdraftPlus: WP Backup & Migration Plugin to version 2.26.16.26 or later, or 1.26.16 or later, where this vulnerability is fixed. No other mitigation is required as the vulnerability is addressed in these releases.

Description

A deserialization vulnerability (CWE-502) exists in the UpdraftPlus: WP Backup & Migration Plugin for WordPress versions before 2.26.16.26 and 1.26.16. This flaw allows users with Subscriber-level roles to plant serialized data that becomes a PHP Object Injection when an administrator performs a backup and restore operation. No known gadget chains currently exist, limiting the demonstrated impact to instantiation of attacker-chosen classes in their own requests. Exploitation requires precise alignment of the planted data with the backup restore process.

References

Community reviews

Loading reviews…