← All security briefings

Attention

UpdraftPlus restore path: subscriber profile text can alter a later database restore (CVE-2026-108761)

Identifiers: CVE-2026-108761

Published
Last substantive change
Last verified

Last verified: . Attention items are due for re-verification within 72 hours.

Summary

Wordfence published CVE-2026-108761 on 18 November 2026 for the UpdraftPlus backup plugin. A logged-in user with only a subscriber role can place crafted text in their profile description. That text is captured in a database backup and, when an administrator later restores the backup on a vulnerable version, is processed as SQL. The vendor released Free 1.26.16 and Premium 2.26.16 on 16 November 2026.

Classification reason: Vendor changelog dated 16 November 2026 marks 1.26.16 as a security release and credits Jakub Herman and Wordfence for further instances of a problem first patched in 1.26.9. The Wordfence record was public on 18 November 2026 and carries its own attribution. Sources checked 18 November 2026. The CNA endpoint returned 404.

Impact

Restoring a tainted backup can modify sensitive WordPress data. On sites where plugin installation is permitted, the researcher states the chain can continue to installing and activating an attacker-controlled plugin, which means code execution. This is not unauthenticated and not immediate. It needs an account, a backup that captured the payload, and an administrator performing a restore.

Who is affected

UpdraftPlus Free up to and including 1.26.15, and Premium 2.0.0 through 2.26.15. Most relevant for sites that allow public registration or hold many low-privilege accounts and that rely on UpdraftPlus database restores.

Products and versions

Products and versionsAffectedFixed
UpdraftPlus Free <= 1.26.15; Premium 2.0.0 - 2.26.15 Free 1.26.16; Premium 2.26.16

Exploitation evidence

Exploitation not established. No real-world exploitation was observed in the sources reviewed. That is not evidence that none exists.

Sources: Wordfence Intelligence

Actions

  1. Update to Free 1.26.16 or Premium 2.26.16 and confirm the installed version.
  2. Keep existing known-good backups. Do not remove your recovery path because of this notice.
  3. Ask your hosting or backup provider to review how far prior backups should be trusted, considering who held accounts when they were taken.
  4. Before restoring any pre-update backup to production, test it on an isolated copy running the updated plugin.
  5. Review whether public registration and plugin installation are actually needed on the site.

Unknowns

  • How updated versions handle backups created before the update was not verified.
  • No CNA record could be retrieved at check time, so only vendor and researcher sources are available.
  • The fix was not independently tested against the researcher's described case.

Sources

  • Wordfence Intelligence · retrieved https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/updraftplus/updraftplus-wp-backup-migration-plugin-12615-and-updraftplus-premium-22615-authenticated-subscriber-second-order-sql-injection-to-remote-code-execution-via-user-profile-description
  • Plugin vendor / WordPress SVN · retrieved https://plugins.svn.wordpress.org/updraftplus/trunk/readme.txt

Change history

  1. — Published: 18 Nov 2026: published. Vendor fix released 16 Nov 2026 (Free 1.26.16 / Premium 2.26.16). Wordfence disclosure 18 Nov 2026. CNA record unavailable at check.

Subscribe: RSS feed · JSON Feed · Feed format and fields