Answer in brief
CVE-2026-121150 records a Unknown severity vulnerability in UpdraftPlus (Free & Pro) - Subscriber+ Privilege Escalation via Backup Restore Comment Discard SQLi. The current sources do not mark it as known exploited. The current feed maps Unknown/UpdraftPlus: WP Backup & Migration Plugin (generic), Unknown/UpdraftPlus: WP Backup & Migration Plugin (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Unknown/UpdraftPlus: WP Backup & Migration Plugin (generic), Unknown/UpdraftPlus: WP Backup & Migration Plugin (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Unknown/UpdraftPlus: WP Backup & Migration Plugingeneric | >=2.0.0 <2.26.16.26 | 2.26.16.26 |
| Unknown/UpdraftPlus: WP Backup & Migration Plugingeneric | >=0 <1.26.16 | 1.26.16 |
Published upstream
Nov 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 21, 2026
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 correctly handle comment-like content found in the middle of a long SQL statement when restoring a database backup, allowing users with a role as low as Subscriber who have stored crafted content in their own profile to have SQL executed when an administrator later restores a backup, and so escalate their account to administrator. This is a different code path from the backup restore issue fixed in 1.26.10, and it does not depend on the database server's maximum packet size.
Quoted source text, attributed separately from HOL analysis.