UpdraftPlus is one of the most widely installed backup plugins for WordPress, so this issue touches a lot of small business sites. On 16 November 2026 the vendor released Free 1.26.16 and Premium 2.26.16. On 18 November 2026 Wordfence published a record for CVE-2026-108761 describing the problem. The Wordfence record lists the affected versions as Free up to and including 1.26.15 and Premium 2.0.0 through 2.26.15. We checked both sources on 18 November 2026. Our shorter briefing is at our UpdraftPlus restore briefing. This article goes deeper into one idea: a backup restore is a trust boundary.
Why a restore is a trust boundary
Most site owners think of a backup as a copy of their own data. In practice a backup is a recovery input, and it can contain untrusted data, because it also holds everything other people have put into the site. According to the Wordfence record, a user with only a subscriber account can write crafted text into their profile description. That field is stored in the database like any other. When UpdraftPlus creates a database backup, the text goes into the backup file.
Nothing happens at that point. The problem appears later. When an administrator restores that backup on a vulnerable version, the stored text is processed as SQL instead of as plain data. The researcher states this can change sensitive WordPress data. On sites where plugin installation is available, the chain can continue to installing and activating a plugin controlled by the attacker, which means code execution on the server.
It helps to be precise about what this is not. It is not an unauthenticated attack. It is not immediate remote code execution. Uploading a backup file alone does not trigger it. Three things have to line up: a low-privilege account that wrote the text, a backup that captured it, and an administrator who later runs a restore. That is why the restore step deserves the same care you would give to installing an unknown plugin.
What the update does and does not do
The vendor changelog marks 1.26.16 as a security release. It describes the fix as covering further related instances of a problem first patched in 1.26.9, where a low-privileged account could manipulate a restore after inserting long controlled sequences into the database. The changelog credits Jakub Herman and Wordfence. The Wordfence record carries its own researcher attribution, so we treat the two credits separately rather than assume they describe the same report.
The update changes how the plugin behaves from now on. It does not reach back into backup files you already have. We have not verified how the updated versions handle a backup created before the update. So we will not tell you that every old backup is now dangerous, and we will not tell you that the patch makes them safe forever. Both claims would go beyond the evidence.
Checklist for site owners
- Update now. Install Free 1.26.16 or Premium 2.26.16 and confirm the version in the plugins screen.
- Keep your known-good backups. Do not delete your recovery path because of this notice. Review how far each backup should be trusted rather than discarding it.
- Ask your provider about prior backups. If a hosting or maintenance provider manages backups, ask them to review how far older backups should be trusted, considering who had accounts when those backups were taken.
- Test restores in isolation first. Before restoring any pre-update backup to production, restore it to an isolated copy running the updated plugin and check the result.
- Review account creation. If your site does not need public registration, turn it off. Fewer low-privilege accounts means less untrusted text in your database.
- Review plugin installation. The researcher ties the code execution step to sites where plugin installation is available. Review whether plugin installation needs to be available on your site, and who can use it.
- Look at restore history. If restores were performed recently, note when and from which backup. That gives your provider something concrete to review.
What we do not know yet
No real-world exploitation was described in the sources we reviewed. That does not mean none exists. The CNA endpoint returned a 404 when we checked, so we cannot cite a CNA record. The affected ranges come from the Wordfence record, and the vendor confirms a security fix in 1.26.16. We have not independently tested the fix.
Sources
- Wordfence record for CVE-2026-108761
- UpdraftPlus readme changelog on WordPress SVN
- UpdraftPlus changeset 3807154
- UpdraftPlus changelog page
If you want help with backup review, isolated restore testing or ongoing monitoring, see our services.