# UpdraftCentral compromise: what to do on your WordPress site

> UpdraftCentral compromise, October 2026: update UpdraftPlus to 1.26.13, delete every connection key by hand, then check users and plugins. Dated, with sources.

Canonical: https://red.run.cloud/learn/updraftcentral-key-compromise-what-to-do · By Timothy Lindblom · Published 2026-11-02 · Updated 2026-11-02

If your WordPress site runs UpdraftPlus, update it to 1.26.13 (free) or 2.26.13 (Premium) or later, then delete the UpdraftCentral connection key on the site by hand. The update alone does not remove a backdoor already installed. After the key is gone, review users and plugins on every site ever connected to UpdraftCentral Cloud, regenerate salts, change administrator passwords, and restore a pre-17 October backup if you find anything.

| Fact | Detail | Source |
|---|---|---|
| What happened | TeamUpdraft says an attacker accessed teamupdraft.com, and that it believes the customer database was accessed, including UpdraftCentral connection keys. Access was identified over the weekend of 17 to 18 October 2026 | [TeamUpdraft](https://teamupdraft.com/blog/security-incident-october-2026/) |
| CVE | None assigned at our check on 2 November 2026. Patchstack calls it a key compromise, not a code flaw | [Patchstack](https://patchstack.com/articles/updraftcentral-key-compromise-wordpress-backdoors/) |
| Fixed versions | UpdraftPlus 1.26.13 (free) and 2.26.13 (Premium), which disconnect connections made before 13:07 BST on 18 October | [TeamUpdraft](https://teamupdraft.com/blog/security-incident-october-2026/) |
| Version trap | The changelog lists 1.26.12 on 19 October and 1.26.13 the same day as "Properly apply the revocation in 1.26.12". The current 1.26.14 (26 October) adds no security change | [Changelog](https://wordpress.org/plugins/updraftplus/#developers) |
| In scope | Sites connected to UpdraftCentral cloud. TeamUpdraft says self-hosted UpdraftCentral is not affected | [TeamUpdraft](https://teamupdraft.com/blog/security-incident-october-2026/) |
| Exploitation | Patchstack saw backdoor plugin installs between 18 October 15:32 and 19 October 09:23 UTC, in 99 distinct plugin names | [Patchstack](https://patchstack.com/articles/updraftcentral-key-compromise-wordpress-backdoors/) |
| Latest vendor update | 29 October 2026: some sites were compromised with no visible sign, and an attacker plugin created a new administrator after the site had been disconnected. Check every site ever connected to UpdraftCentral Cloud, free or Premium | [TeamUpdraft](https://teamupdraft.com/blog/security-incident-october-2026/) |
| Checked | 2 November 2026 | this page |

## Who is affected?

Sites connected to UpdraftCentral cloud are the core group. TeamUpdraft says [self-hosted UpdraftCentral is not affected](https://teamupdraft.com/blog/security-incident-october-2026/), and that UpdraftPlus plugin files, downloads and backups in your own remote storage were not part of the breach. It adds that if your site was accessed through UpdraftCentral, you should also re-authorise your remote storage and change any storage access keys as a precaution. Its notice also covers UpdraftVault and UpdraftClone keys, with separate steps for each.

Patchstack adds a point many owners miss. The UpdraftCentral client ships inside every copy of UpdraftPlus and stays dormant until a key exists. Connecting a TeamUpdraft account [can create a key through a checkbox that is ticked by default](https://patchstack.com/articles/updraftcentral-key-compromise-wordpress-backdoors/), and Nethemba [describes the same default](https://nethemba.com/updraftcentral-backdoor-analysis/). So a site can hold a key its owner never meant to create.

## Why does "keep plugins updated" not cover this?

There is no vulnerable code to patch. Patchstack says attackers used [genuine dashboard signing keys](https://patchstack.com/articles/updraftcentral-key-compromise-wordpress-backdoors/) to send commands that the site accepts as legitimate, and that keys do not expire. It reports that keys issued in November 2025 still worked in October 2026. A fully patched plugin still obeys a valid key.

Three things follow:

1. **The update revokes only part of the keys.** TeamUpdraft says 1.26.13 and 2.26.13 [disconnect connections made before 13:07 BST on 18 October](https://teamupdraft.com/blog/security-incident-october-2026/). A key made after that time is outside that sentence. Nethemba [lists the same gap](https://nethemba.com/updraftcentral-backdoor-analysis/) and says to delete keys by hand anyway.
2. **Version 1.26.12 is not enough.** The [changelog](https://wordpress.org/plugins/updraftplus/#developers) shows a 19 October 1.26.12 entry on revocation, followed the same day by 1.26.13 to "properly apply" it. Older advice that says "update to 1.26.12" is out of date.
3. **The update does not clean up.** TeamUpdraft's notice describes the update as disconnecting connections, and tells owners to check for [unexpected plugins, activity and users](https://teamupdraft.com/blog/security-incident-october-2026/).

## How do I fix it?

TeamUpdraft's own order for UpdraftCentral cloud users, per site, is below. Do each step in the site's own WordPress dashboard, not through UpdraftCentral.

### If you manage the site yourself

- [ ] Update UpdraftPlus to 1.26.13 (free) or 2.26.13 (Premium) or later.
- [ ] Delete the connection key at Settings, UpdraftPlus Backups, Advanced Tools, UpdraftCentral. Patchstack says removing the site from the dashboard alone is not enough. On WP-CLI, TeamUpdraft gives `wp option delete updraft_central_localkeys`.
- [ ] Under Users, remove any administrator you do not recognise. Look for Editor accounts too: [Patchstack describes](https://patchstack.com/articles/updraftcentral-key-compromise-wordpress-backdoors/) a hidden Editor that has been granted extra capabilities, and says to find it by capability, not by name.
- [ ] Under Plugins, including the Must-Use tab if shown, note anything you did not install. Do not delete it in wp-admin. Deactivate it and move it out of the web root, as the caution below explains, so the traces stay. TeamUpdraft names Site Health Cache, Asset Forge 2, Core Smith, Data Engine Cc0, Image Forge, Quick Pack, Seo Helper and WP Forge, and says to check the folders over SFTP or SSH, because some hide from the dashboard.
- [ ] Regenerate the WordPress salts (`wp config shuffle-salts`, or ask your host), then change the password of every administrator and Editor account.
- [ ] If your site was accessed through UpdraftCentral, re-authorise your remote storage and change any storage access keys, as TeamUpdraft advises.
- [ ] If you found anything, restore from a backup taken before 17 October, as TeamUpdraft advises. [Choosing a clean restore point](/learn/restored-backup-still-hacked-clean-restore-point) explains how to check it.
- [ ] Reconnect to UpdraftCentral only when you need it. Patchstack's advice was to wait until the vendor explains the cause; that is its 19 October position.

If you use WP-CLI, [Patchstack gives a check for keys](https://patchstack.com/articles/updraftcentral-key-compromise-wordpress-backdoors/): `wp option get updraft_central_localkeys`. Any output means a key exists. [Nethemba's read-only check script](https://nethemba.com/updraftcentral-backdoor-analysis/) is meant to run with `--skip-plugins --skip-themes`, because an installed backdoor can crash WP-CLI.

Patchstack adds a caution for a plugin you suspect: deactivate it and move it out of the web root instead of deleting it in wp-admin, because it says the uninstall routine erases traces. Do not try to repair a broken-looking plugin, since Patchstack says fixing its error activates the backdoor.

Also change your teamupdraft.com password by typing the address yourself, and reset two-factor there, [as TeamUpdraft lists](https://teamupdraft.com/blog/security-incident-october-2026/). [Nethemba says](https://nethemba.com/updraftcentral-backdoor-analysis/) UpdraftPlus Premium may store that password in the site database.

### If a host or agency manages the site

Send this and keep the reply:

> For **[your domain]**: please confirm UpdraftPlus is at 1.26.13 or 2.26.13 or later, that the UpdraftCentral connection key has been deleted on the site, and that you have reviewed administrator and Editor users, plugins and Must-Use plugins. Tell me the date and time you did each, and whether the site was ever connected to UpdraftCentral.

- [ ] Ask for the reply in writing, with times.
- [ ] Ask whether other remote-management tools (for example MainWP or ManageWP) also hold connections, and who holds the login for each.

## Which other remote-management connections do I have?

This incident is one instance of a pattern: a vendor-held key opens many sites, and [which other plugins hold such keys](/learn/which-plugins-hold-remote-control-keys) is covered on its own page. Agencies should also read why [management plugins are a single point of failure](/learn/agency-management-plugins-single-point-of-failure). Make a short list of every tool that can send commands to your site, who holds its login, and when its key was last rotated. Delete connections you do not use. We have no primary source about a compromise of any tool other than UpdraftCentral; this list is housekeeping, not a claim about them.

## Am I affected?

<div class="ln-selftest">
<h3>Am I affected? Where you stand right now</h3>
<p>There is no CVE here, so a version lookup has little to match. From outside, nobody can see whether a key exists on your site or who holds it.</p>
<ol>
<li><span class="ln-state ln-state-detected">Detected</span> <strong>UpdraftPlus is visible on the site and the version is below 1.26.13 or 2.26.13.</strong> That says the keys may not have been revoked. Update and delete the key today.</li>
<li><span class="ln-state ln-state-unknown">Unknown</span> <strong>The version is hidden, or it is current but you have not looked at keys, users and plugins.</strong> This is the common case. A current version does not tell you about a key made after the cutoff or a backdoor installed before the update.</li>
<li><span class="ln-state ln-state-confirmed">Confirmed by owner evidence</span> <strong>You have seen the key list empty in Advanced Tools or via WP-CLI, and you reviewed users and plugins, from inside the site, including the `wp-content/plugins` and `wp-content/mu-plugins` folders on the filesystem.</strong> Nethemba documents plugins hidden from dashboard lists, so the lists alone are not enough. Note the date. If the review found a backdoor, treat the site as compromised and restore.</li>
</ol>
<p>No scan, ours included, moves you from "unknown" to "confirmed".</p>
</div>

## Was anything installed on my site?

TeamUpdraft says the attacker [used connections to user sites to create admin accounts and install malicious plugins](https://teamupdraft.com/blog/security-incident-october-2026/) and that the full extent is unknown. Look for these, from Patchstack's and Nethemba's reports:

| Sign | Where to look |
|---|---|
| A plugin you did not install | Plugins list and the `wp-content/plugins` folder. Names vary, so do not rely on a name. Patchstack says every sample shares one description line: "Small maintenance toolkit: keeps option storage tidy." |
| An Editor account holding administrator-level capabilities | Users list, or a capability query. Patchstack reports the `@example.org` email domain and the display name "Site Tools" |
| A database option ending in `_sync_token` | Options table, via WP-CLI or your host's database tool |
| The log line "Command received: plugin.upload_plugin" | UpdraftCentral log, as [Patchstack describes](https://patchstack.com/articles/updraftcentral-key-compromise-wordpress-backdoors/). Its access-log checks look at the User-Agent and an activation request, not this message |
| A WordPress fatal-error email naming an unfamiliar plugin | Your admin inbox. Patchstack and Nethemba both say early samples crashed uncached pages |

If the Users list looks wrong, [how to find a hidden WordPress admin](/learn/find-a-hidden-wordpress-admin) goes further. Nethemba says one variant [leaves no account and no database trace](https://nethemba.com/updraftcentral-backdoor-analysis/), so the access log may be the only evidence. An ordinary-looking user list does not prove nothing was installed. Patchstack also says a few installs never activated, and those sites should still be treated as affected.

## What is the bug, without the details?

There is no code bug to patch. The site trusts commands signed with a dashboard key. If the key leaks, whoever holds it can ask the site to install a plugin through WordPress's normal installer. The vendor says it has [brought in an external security firm](https://teamupdraft.com/blog/security-incident-october-2026/) (its 21 October update), and that [WordPress.org pushed the update out to all users](https://teamupdraft.com/blog/security-incident-october-2026/) (its 20 October update). Its 29 October update adds that an attacker plugin created a new administrator after a site had been disconnected, so an empty key list does not end the check. The notice is the first place to check for new steps. Patchstack and Nethemba publish their own indicators and update them.

If you also run PHP on the same server, the [PHP2Shell vulnerability write-up](/learn/php2shell) was disclosed within days of this. It is a separate issue with its own fix. The tracker lists the other October incidents, and [what October's incidents mean for small businesses](/learn/october-2026-incidents-small-businesses) covers where to start. More in [the other WordPress guides](/learn/topics/wordpress).

## Questions people ask

### UpdraftPlus hacked, what do I do?

Update UpdraftPlus to 1.26.13 (free) or 2.26.13 (Premium) or later, then delete the UpdraftCentral connection key on the site yourself. After that, look at your users and plugins, including the Must-Use list, for anything you did not add, on every site ever connected to UpdraftCentral Cloud. Regenerate the WordPress salts and change administrator passwords. If you find something, restore from a backup taken before 17 October.

### Does updating UpdraftPlus remove the backdoor?

No. The vendor's notice describes the update as disconnecting old connections. It says nothing about removing plugins or accounts that were already created, and puts that check on the site owner. Patchstack and Nethemba both say an installed backdoor stays until someone removes it.

### I never used UpdraftCentral. Do I still need to check?

Yes, a quick check. Patchstack and Nethemba both report that connecting a TeamUpdraft account can create a key through a box that is ticked by default, so a site can hold a key its owner never chose to make. Look for a key in the UpdraftCentral section of the plugin's Advanced Tools.

### Is this a vulnerability in the UpdraftPlus plugin?

Patchstack says it is not: attackers used genuine dashboard keys, and it is a key compromise, not a code flaw. No CVE was assigned at our check on 2 November 2026. That is why a vulnerability lookup by version has little to match here.

### Is this the same thing as PHP2Shell?

No. PHP2Shell is a pair of bugs in PHP itself. The UpdraftCentral incident is about stolen connection keys. The two overlapped in time, so a WordPress site can need both fixes, and each needs its own check.


## Sources

1. [TeamUpdraft: security incident, October 2026 (vendor notice, last updated 29 October 2026 16:01 GMT)](https://teamupdraft.com/blog/security-incident-october-2026/): The vendor's own account, timeline and remediation steps. Check its update log before acting; it changed several times between 19 and 29 October. Read 2 November 2026.
2. [Patchstack: UpdraftCentral key compromise and WordPress backdoors (19 October 2026)](https://patchstack.com/articles/updraftcentral-key-compromise-wordpress-backdoors/): Independent telemetry and indicators. Patchstack says no CVE applies and calls it a key compromise, not a code flaw.
3. [Nethemba: UpdraftCentral backdoor analysis (status 22 October 2026)](https://nethemba.com/updraftcentral-backdoor-analysis/): Researcher analysis of how the backdoor plugins behave and persist, with a read-only check script.
4. [UpdraftPlus changelog (wordpress.org plugin page)](https://wordpress.org/plugins/updraftplus/#developers): Entries for 1.26.12 and 1.26.13, both dated 19 October 2026, and 1.26.14 on 26 October with no security entry. Read 2 November 2026.
5. [WordPress.org support thread: Security vulnerability affecting UpdraftPlus 1.26.11](https://wordpress.org/support/topic/security-vulnerability-affecting-updraftplus-1-26-11/): Site owners' first reports. Owner posts, not a vendor statement.
