Skip to main content
CVE-2026-121153VulnerabilityPublished

The UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup & Migration

Source GCVE Database

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-121153· High

Not known to be exploited : upgrade to 2.26.16.26 soon.

Data as of 21 Nov 2026, 07: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

If you cannot patch yet, administrators should exercise caution when performing database search and replace or migration restore operations, especially if untrusted users have Subscriber roles.

Description

A vulnerability in the UpdraftPlus: WP Backup & Migration Plugin for WordPress before versions 2.26.16.26 and 1.26.16 allows users with Subscriber roles to inject data into their own user meta. This data can be rewritten into a live PHP object when an administrator performs a search and replace or migration restore, which WordPress later instantiates. The vulnerability does not include a gadget chain in WordPress core or the plugin itself, so further impact depends on other installed classes.

References

Community reviews

Loading reviews…