UpdraftPlus backup flaws affect both the Free and Pro WordPress plugins before their November fixes. Three CVEs share the same patch boundary, but they need different conditions. A Subscriber can plant data; administrator restore or search and replace work, plus a later read for the object injection paths, is needed for the described effects.
The decision for site owners is to update the installed branch and review recent privileged maintenance. Use the vulnerability intelligence platform as a reference point when prioritizing this plugin issue across sites. The plugin version and maintenance history still need checks inside each site.
UpdraftPlus Backup Flaws: What Does Each CVE Require?
WPScan lists the same fixed versions for all three entries: Free 1.26.16 and Pro 2.26.16.26. The table separates the attacker-controlled data, later administrative action, and stated outcome. A vulnerable installation alone does not prove that the later action occurred.
| CVE | Where the flaw appears | Later action | Potential result |
|---|---|---|---|
| CVE-2026-121152 | Unsafe handling of external database dump output for large tables | Administrator restores a backup | Stored profile data becomes SQL that can raise privileges |
| CVE-2026-121153 | Serialized data crosses the search and replace recursion limit | Administrator runs search and replace or a migration restore; WordPress reads the result | A planted PHP object may be instantiated |
| CVE-2026-121154 | Search and replace leaves serialized string lengths inconsistent | Administrator runs a URL-lengthening replacement or migration restore; WordPress reads the result | Trailing data may be parsed as a PHP object |
The first row is a backup and restore problem. The other rows concern database search and replace during maintenance. WPScan rates each entry 7.1, high, but the pages do not label that score as CVSS 3.1 or 4.0.
How Can a Subscriber’s Data Cross the Restore Boundary?
For CVE-2026-121152, the WPScan CNA record says a Subscriber can store profile data before a large-table backup. UpdraftPlus does not safely process the external dump tool’s output in affected versions. When an administrator later restores that backup, the stored data can become executed SQL.
The record gives administrator-role assignment as an example consequence. It does not say that every backup triggers the flaw or that a Subscriber can run the restore themselves. Keep the account’s write and the later administrator restore as separate events when reviewing exposure.
Our earlier UpdraftPlus restore SQL injection profile covers a different CVE. Compare identifiers and the maintenance event before joining alerts or case notes. Similar product and outcome wording does not establish a single incident.
Why Are the Two PHP Object Injection Paths Different?
CVE-2026-121153 concerns the recursion limit in the plugin’s search and replace process. WPScan’s CNA record says a Subscriber can place data in their own user metadata. A later administrator search and replace or migration restore rewrites that data; WordPress can instantiate an object on a subsequent read.
CVE-2026-121154 concerns the declared length of a serialized string. The CNA record says a longer replacement can leave that length inconsistent with the stored value. A later read may interpret trailing bytes as another serialized structure, including an attacker-chosen object.
Both records describe PHP object injection, but they identify different processing failures. The CVE-2026-121154 record says further impact depends on classes available from other installed code. The CVE-2026-121153 record also ties further impact to a suitable class outside WordPress core and UpdraftPlus.
These conditions matter in a mixed plugin estate. Object creation is the described weakness; a specific downstream effect needs evidence from the site’s installed code and logs. Our other UpdraftPlus object injection profile describes another identifier, so keep case records distinct.
Which Versions and Maintenance Events Should Be Checked First?
Start with the plugin edition and installed version, then compare it with WPScan’s fixed boundary. Free installations below 1.26.16 and Pro installations below 2.26.16.26 fall within the listed affected range. Confirm the active plugin version after updating; a downloaded package is not proof of deployment.
Next, identify who had Subscriber access and when administrators ran backup restore, migration restore, or database search and replace. Review whether such work occurred while an affected version was installed. This is a defensive triage sequence derived from the CNA descriptions, not a published detection signature.
- Record the active UpdraftPlus edition and version on each site.
- Update Free to 1.26.16 or later, or Pro to 2.26.16.26 or later.
- Verify the active version and preserve change records after deployment.
- Review administrator restore, migration, and search and replace events during the affected period.
- Correlate those events with unexpected account-role changes or application errors.
- Preserve relevant logs and backup metadata if an event looks suspicious.
Prioritize sites with an affected version and recent administrator maintenance. If a restore is planned, verify the update and use a trusted backup under the organization’s recovery procedure. The immutable backup glossary explains one way to protect backup copies, although immutability does not repair the plugin flaw.
How Should Teams Prioritize These Three CVEs?
Brandefense Blackhole counted one dark-chat post matching CVE-2026-121152 from August 24 through November 22, 2026. It counted one matching post for CVE-2026-121154 over the same period. These are per-CVE post counts; the sets may overlap and must not be added.
A matching discussion is a research signal, not evidence of exploitation on a WordPress site. The CVE descriptions establish a potential chain, while a site investigation must establish whether the required administrator action occurred. Use installed version and maintenance history to decide which systems need urgent review.
How Should the Comparison Guide the Response?
Patch both branches to the versions WPScan lists, even if only one of the three mechanisms appears relevant to a site. Then separate backup restore from search and replace activity in the incident timeline. The distinction determines which administrative records and later database reads deserve attention.
The sources describe possible privilege escalation for CVE-2026-121152 and conditional object injection for the other two. They do not identify a specific compromised site in these records. Document the evidence for each CVE separately before assigning an outcome to an affected installation.
Frequently Asked Questions
Which UpdraftPlus versions should administrators install?
WPScan lists 1.26.16 for the Free branch and 2.26.16.26 for Pro as the fixed versions for all three entries. Verify the active version after the update.
Does a Subscriber need to run the restore?
The records describe a Subscriber planting data and an administrator later running a backup restore, migration restore, or search and replace. Keep those roles and events separate.
What evidence should a site owner review after updating?
Review privileged maintenance history, account-role changes, relevant application errors, and available backup records. An affected version alone does not establish that an attack chain completed.
Sources
- WPScan, CVE-2026-121152 vulnerability entry, November 19, 2026
- WPScan, CVE-2026-121153 vulnerability entry, November 19, 2026
- WPScan, CVE-2026-121154 vulnerability entry, November 19, 2026
- WPScan CNA, CVE-2026-121152 record, November 21, 2026
- WPScan CNA, CVE-2026-121153 record, November 21, 2026
- WPScan CNA, CVE-2026-121154 record, November 21, 2026
