Skip to main content
Menu
CVEs

UpdraftPlus: WP Backup & Migration Plugin PHP object injection in search and replace

CVE-2026-121153Published November 21, 2026, updated

Exploited
No known exploitation
Fix
Fixed in 2.26.16.26, 1.26.16
Who is exposed
Not reported

Summary

The UpdraftPlus: WP Backup & Migration Plugin WordPress plugin does not keep serialized data inert when its database search and replace hits the recursion limit. Any logged-in user, even one with the Subscriber role, can plant data in their own user meta. When an administrator later runs a search and replace or migration restore, that data becomes a live PHP object, which WordPress instantiates on a later read, enabling PHP object injection. Further impact depends on a suitable class from another installed copy of the plugin.

Written by a model

Original description

The UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 1.26.16 do not keep a serialized value inert when their database search and replace reaches its recursion limit, allowing users with a role as low as Subscriber to plant data in their own user meta that is rewritten into a live PHP object when an administrator later runs a search and replace or a migration restore, and is then instantiated by WordPress on a later read.

This is distinct from CVE-2024-10957, whose fix restricted the unserialize call but left this path in place. No gadget chain is present in WordPress core or the UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 1.26.16 themselves; further impact depends on a suitable class from another installed UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 1.26.16 or .

What to do

Upgrade to a fixed version: 2.26.16.26, 1.26.16.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-121153 (UpdraftPlus (Free & Pro) - Subscriber+ PHP Object Injection via Search and Replace Recursion Limit), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-121153 (entry last updated 2026-11-21):
Affected:
- Unknown UpdraftPlus: WP Backup & Migration Plugin: from 2.0.0, fixed in 2.26.16.26
- Unknown UpdraftPlus: WP Backup & Migration Plugin: fixed in 1.26.16
Fixed versions: 2.26.16.26, 1.26.16.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-121153 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-121153 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- the references on https://cve.now/CVE-2026-121153
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-121153
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-121153"}.

Affected versions

cve.now Index

0Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 55 if added to CISA KEV
  • Would score about 50 if CISA's SSVC rates exploitation active
  • Would score about 22 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 3

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-121153
RecordNVD · CVE-2026-121153
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
Exploitwpscan.com · vulnerability/608b4355-fdb4-4462-b58b-443feb77992b

Questions about CVE-2026-121153

Is CVE-2026-121153 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-121153?

UpdraftPlus: WP Backup & Migration Plugin: from 2.0.0 before 2.26.16.26. UpdraftPlus: WP Backup & Migration Plugin: before 1.26.16.

Source: cve.now feed data

How do I fix CVE-2026-121153?

Upgrade to a fixed version: 2.26.16.26, 1.26.16.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.