Skip to main content
Menu
CVEs

UpdraftPlus: WP Backup & Migration Plugin privilege escalation via SQL injection in backup restore

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

Exploited
No known exploitation
Fix
Fixed in 1.26.10, 2.26.10.26
Who is exposed
Not reported

Summary

The UpdraftPlus: WP Backup & Migration Plugin WordPress plugin has a flaw in its database restore process. A user with Subscriber-level access can store crafted content in their own account, and when an administrator later restores a backup, that content triggers an SQL injection that raises the user's privileges to administrator.

Written by a model

Original description

The UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 1.26.10, UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 2.26.10.26 does not guard all execution paths of its database restore process against second-order SQL injection, allowing a Subscriber-level user who has stored crafted content in their own account to escalate to administrator when an administrator later restores a backup. This is due to an incomplete fix of CVE-2026-108761 in 1.26.9: the fix guards only one of the restore routine's execution paths, and a second path remains exploitable.

What to do

Upgrade to a fixed version: 1.26.10, 2.26.10.26.

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-111067 (UpdraftPlus (Free & Pro) - Subscriber+ Privilege Escalation via Backup Restore SQLi), 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-111067 (entry last updated 2026-11-21):
Affected:
- Unknown UpdraftPlus: WP Backup & Migration Plugin: from 1.26.9, fixed in 1.26.10
- Unknown UpdraftPlus: WP Backup & Migration Plugin: from 2.26.9.26, fixed in 2.26.10.26
Fixed versions: 1.26.10, 2.26.10.26.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-111067 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-111067 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-111067
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-111067
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-111067"}.

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-111067
RecordNVD · CVE-2026-111067
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
Exploitwpscan.com · vulnerability/20ece3e4-3c28-4ec3-9890-1739d9aee01e

Questions about CVE-2026-111067

Is CVE-2026-111067 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-111067?

UpdraftPlus: WP Backup & Migration Plugin: from 1.26.9 before 1.26.10. UpdraftPlus: WP Backup & Migration Plugin: from 2.26.9.26 before 2.26.10.26.

Source: cve.now feed data

How do I fix CVE-2026-111067?

Upgrade to a fixed version: 1.26.10, 2.26.10.26.

Source: cve.now feed data

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