Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

UpdraftPlus Database Restore Object Injection (CVE-2026-121151)

CVE-2026-121151 is a PHP object injection flaw in the UpdraftPlus WordPress backup plugin.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
3 min read
CVE ID
CVE-2026-121151
Vendor
UpdraftPlus
Affected Product
UpdraftPlus: WP Backup & Migration Plugin (Free and Pro)
Exploitation
Not confirmed
Published
2026-11-19

WPScan says long database values are not preserved byte for byte during a restore. A Subscriber can plant a serialized value, but an administrator must subsequently back up and restore the database for the described injection to occur.The CNA record says the demonstrated effect is instantiation of an attacker-chosen class in the attacker's own requests. It states that no gadget chain is known in the affected plugin or WordPress core. This record does not establish automatic remote code execution.

What it allows

How Does CVE-2026-121151 Reach the Restore Process?

The attacker first needs a WordPress account with at least Subscriber access and a place to plant a serialized database value. The dangerous change occurs later, when an administrator backs up and restores that database with an affected UpdraftPlus version. WPScan says restoration can change long values rather than preserve their bytes.

The CNA description adds an important constraint: the planted value must align with how the backup is read back. That depends on the row and dump format. The record's demonstrated result is class instantiation in the attacker's own requests, while the absence of a known gadget chain limits the stated impact.

This is a conditional workflow risk, so defenders should review both account access and recent restore activity. The related Brandefense product page is Vulnerability Intelligence platform. The vulnerability prioritization glossary explains how exposure conditions change patch priority.

Brandefense Blackhole counted one dark-chat post mentioning CVE-2026-121151 from 23 August through 21 November 2026. The measured unit is a post mentioning this identifier, not an affected site or verified attack. Discussion alone does not prove exploitation.

Who is affected

Which UpdraftPlus Versions Need Attention?

The WPScan advisory lists fixes in 1.26.16 and 2.26.16.26 for the Free and Pro lines. The WPScan CNA record marks versions from 0 up to, but excluding, 1.26.16 as affected. It separately marks 2.0.0 up to, but excluding, 2.26.16.26 as affected.

Check the installed plugin's complete version, including the fourth component in the 2.x branch. Also record whether Subscriber or higher accounts can add database values and whether administrators use backup restores. The CNA's exploit condition includes those workflow steps; an affected version alone does not show that an injection occurred.

Use the patch management workflow to record the update and verify the active plugin version afterward. If a restore is planned before updating, restrict access to accounts that can plant database values and review the backup source. Those are our defensive precautions, not a vendor-published mitigation.

What to do

  1. Inventory UpdraftPlus installations

    Identify Free and Pro installations, record the full plugin version, and map accounts with Subscriber or higher access. Prioritize sites that use database backup and restore workflows.

  2. Update the affected branch

    Update the 1.x branch to at least 1.26.16 or the 2.x branch to at least 2.26.16.26, using the correct UpdraftPlus package for each site.

  3. Verify the active version

    After updating, check the running plugin version on each site. Confirm the complete 2.x version string rather than treating 2.26.16 alone as the published fix.

  4. Review account and restore history

    Review recent account changes and administrator backup restores on affected sites. Correlate the timing of those events; a restore by itself does not prove this CVE was used.

What Brandefense can do

Frequently Asked Questions

Can a Subscriber trigger the issue alone?

The CNA record says a Subscriber can plant the value, but the described injection follows an administrator's backup and restore of the database.

Does CVE-2026-121151 prove remote code execution?

No. WPScan's CNA record reports class instantiation in the attacker's own requests and says no gadget chain is known in the plugin or WordPress core.

Which UpdraftPlus versions contain the fix?

WPScan lists 1.26.16 and 2.26.16.26 as the fixed versions for the respective branches. Verify the complete installed version after updating.

Is this CVE in CISA's KEV catalog?

It was absent from CISA's catalog version 2026.11.20, checked on 21 November 2026. Catalog absence does not establish whether exploitation has occurred.

Sources

  1. UpdraftPlus (Free & Pro) Subscriber+ PHP Object InjectionWPScan
  2. CVE-2026-121151 recordWPScan CNA via CVE.org
  3. CVE-2026-121151NIST NVD
  4. Known Exploited Vulnerabilities CatalogCISA
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →