1. Red
  2. Learn
  3. WordPress

Can a plugin vendor access my site? Remote-control keys

Can a plugin vendor access my site? Yes, if you connected a management key. How to inventory vendor-held keys, revoke them, and what October 2026 showed.

By Timothy Lindblom, FounderPublished 2 November 20268 min readHow we check facts
On this page
  1. How can a plugin vendor reach my site?
  2. What did the October 2026 cases show?
  3. How do I inventory and revoke vendor keys?
  4. Am I affected?
  5. Was anything installed, and how do I find a backdoor the plugin list does not show?
  6. What is the general pattern?

Yes, if a plugin or service holds a connection to your site. The sources name three examples: a remote-management key the vendor holds (UpdraftCentral), a script your pages load from the vendor's domain (Brevo), and a plugin file the vendor ships (Rank Math). List every connected dashboard, delete the ones you do not use, and rotate the rest.

For the third example, Rank Math's notice says the plugin files of its PRO 3.0.123 download, available from 20:02 UTC on 15 October to 07:12 UTC on 16 October 2026, contained malware that could compromise a site if the plugin was activated.

FactDetailSource
CaseUpdraftCentral connection keys, held by TeamUpdraftTeamUpdraft
Breach windowUnauthorised access identified over the weekend of 17 to 18 October 2026; the vendor reports customer data was accessed, including connection keysTeamUpdraft
Fixed versionsUpdraftPlus 1.26.13 (free) and 2.26.13 (Premium) or later, published 19 October; disconnects connections made before 13:07 BST on 18 OctoberTeamUpdraft
Version trap1.26.12 / 2.26.12 deletes no key because of a bugNethemba
Keys the update missesCreated 18 October 2026 between 12:07 and 21:00 UTC; delete by handNethemba
Backdoor variants99 distinct plugin names observedPatchstack
Second caseBrevo: a Cloudflare API key used to run a Worker that altered Brevo-served pages and scripts, 14 September 2026, impact 15:01 to 20:30 UTC per BrevoBrevo
Third caseRank Math PRO 3.0.123 download with malware, 15 to 16 October 2026Rank Math
CheckedAt our check on 2 November 2026this page

How can a plugin vendor reach my site?

The sources name several connection channels. Three examples, each with a different trace:

Trust channelWhat the vendor holdsWhere to look
Management connectorThe other half of a key pair, so the vendor's dashboard can send commands your site obeysThe plugin's own settings screen for a connection or dashboard section
Script served from the vendorControl of a file or domain your pages load on every visitPage source for third-party script tags, and your form, chat and tracking embeds
Plugin files the vendor shipsThe download or update you installFiles on disk, the plugin's version and the vendor's notices

Nethemba describes the first channel for UpdraftCentral: the site generates a key pair and the service keeps the dashboard's private key, and the site runs each signed command with the rights of the user who created the key. The site cannot tell a real command from a stolen-key command, because both are validly signed.

What did the October 2026 cases show?

UpdraftCentral. TeamUpdraft says unauthorised access was identified over the weekend of 17 to 18 October and that the data reportedly accessed includes UpdraftCentral connection keys. Patchstack observed 99 distinct backdoor plugin names installed through the channel, with the first installation it saw at 15:32 on 18 October. Nethemba reports that commands again reached two of its sites on 21 October, between 07:10 and 09:21 UTC, after their keys had already been deleted, and that its blocking plugin stopped them. TeamUpdraft's 29 October update adds that some sites were compromised with no visible sign, and that an attacker plugin created a new administrator after the site had been disconnected, so it asks free and Premium users to check every site ever connected to UpdraftCentral Cloud. We found no published count of affected sites in a primary source, so this page gives none.

The trap. Patchstack reports that the option "Add this website to UpdraftCentral" is pre-ticked when a TeamUpdraft account is connected. A site can hold a key its owner does not remember creating.

Brevo. A different mechanism. Brevo's notice says an attacker used a long-lived Cloudflare API key to deploy a Worker. It was routed to all of brevo.com from 15:01 UTC on 14 September, and at 16:07 UTC it was updated to add a loader to three embedded JavaScript files and routed to sibforms.com. Brevo lists the affected items as brevo.com and related domains, sibforms.com and the forms script, the Conversations widget and the SDK loader. It ends the impact at 20:30 UTC. It says its app, API, email sending and customer account data were not affected, and that the widget, SDK and forms were not modified at their source.

Brevo's notice says the Worker showed selected visitors a fake verification page, and that on WordPress sites it tried to install and activate a plugin when a logged-in administrator visited. Its advice is to check for plugins installed or activated on 14 September.

Sansec's researchers, writing on 16 September, give slightly different times (16:05 to 20:12 UTC), say the plugin was fetched from an attacker-controlled host and was not recovered, and estimate more than 100,000 customer sites served the script. That figure is Sansec's estimate from a web search, not Brevo's. Sansec advises comparing the plugin directory on disk with what the admin screen lists.

Rank Math. The vendor channel here was the download itself. Rank Math says an activated 3.0.123 should be treated as compromised, with a restore from a backup taken before 20:02 UTC on 15 October, and that 3.0.124 is the clean version. See our Rank Math check.

In all three cases the weak point sat with the vendor. Keeping your own plugins updated could not have closed it.

How do I inventory and revoke vendor keys?

Do this in order. The order for UpdraftCentral follows TeamUpdraft's own list.

What do I do if I use UpdraftPlus?

Ask the person who manages the site, or check yourself:

Is this site connected to UpdraftCentral or a TeamUpdraft account? Please send the UpdraftPlus version, the list of keys on the UpdraftCentral screen with their creation dates, and the administrator and editor accounts created since 17 October 2026.

  • Log in to the site's own WordPress dashboard, not through UpdraftCentral.
  • Update to 1.26.13 or 2.26.13 or later. TeamUpdraft says this disconnects connections made before 13:07 BST on 18 October. Nethemba reports 1.26.12 deletes no key because of a bug, so do not stop there.
  • Open Settings, UpdraftPlus, Advanced Tools, UpdraftCentral and delete every key listed, including any created on 18 October between 12:07 and 21:00 UTC, which Nethemba says the update does not delete.
  • Check Users for administrator or editor accounts you do not recognise.
  • Check Plugins, including the Must-Use tab, for items you did not install. Patchstack notes that the description is a more reliable sign than the plugin name. Some variants hide from this screen, so also use the file and database checks below.
  • Change administrator passwords. If anything looks wrong, TeamUpdraft says to consider restoring from a backup taken before 17 October.
  • Reconnect to UpdraftCentral only if you still want it, and only after the steps above.

What about every other plugin with a connector?

Agencies that run many sites from one dashboard carry the same exposure, as the management-plugin write-up shows.

  • List each plugin or service that links the site to a vendor dashboard, cloud account or remote manager.
  • Write down who holds the other half of the key, and when the connection was made.
  • Remove the connection for anything you do not use weekly. Reconnect later with a fresh key if you need it.
  • For script embeds (forms, chat, tracking), decide whether the page needs to load code from outside your own domain.

WordPress.org guideline 8 bars plugins from installing plugins from servers other than WordPress.org when the plugin is not acting as a service. It permits services that interact with a site and push software to it, provided the service handles the interaction on its own domain and not within the WordPress dashboard.

Am I affected?

Am I affected? Where you stand right now

From outside, a scan can see which plugins and scripts a site serves. It cannot see a key stored in your database or whether a vendor's key was copied.

  1. Detected The site serves UpdraftPlus below 1.26.13. Treat it as in scope for the steps above if the site is connected to UpdraftCentral cloud; TeamUpdraft says self-hosted UpdraftCentral is not affected (its page, last updated 29 October 2026). Check the key list and the Users and Plugins screens.
  2. Unknown The plugin version is hidden, or you cannot say whether a key exists. This is the usual case. Open the plugin's connection screen or ask whoever runs the site. A Brevo embed alone does not confirm anything either way. Brevo puts its impact between 15:01 and 20:30 UTC on 14 September 2026 and Sansec between 16:05 and 20:12 UTC. It matters mainly if an administrator was logged in and visited a page with a Brevo embed in that period, so check for plugins installed or activated that day.
  3. Confirmed by owner evidence You have a key list with no entry you cannot explain, every key from the 18 October 12:07 to 21:00 UTC window deleted by hand, the fixed version, and a dated review of Users, Plugins, Must-Use plugins, the plugin folders on disk and the database options described below. Recognising a key is not enough: [Nethemba reports that stolen keys keep working until the site deletes them](https://nethemba.com/updraftcentral-backdoor-analysis/). This is owner evidence for that plugin only. It says nothing about your other connectors.

No scan, ours included, moves you from "unknown" to "confirmed".

Was anything installed, and how do I find a backdoor the plugin list does not show?

Deleting a key stops new commands. It does not remove what was already added. Patchstack's guidance is that a site with the backdoor account or trigger should be treated as fully compromised, with a restore from a backup that predates the attack.

Do not rely on the Plugins screen alone. Nethemba reports that some variants remove themselves from the admin plugin list, and Sansec advises comparing the plugin directory on disk with what the admin screen lists.

WhereWhat to look forSource
Files on diskFolders you did not install in wp-content/plugins, wp-content/mu-plugins and wp-content/upgrade (a failed install can leave an unpacked plugin)Nethemba
Must-use pluginsEntries in the separate Must-Use list; they do not appear among normal pluginsTeamUpdraft, WordPress docs
Database optionsWhether the site still holds a key (Patchstack reads it with wp option get on updraft_central_localkeys), and options ending in _sync_token or other per-plugin entries Nethemba listsPatchstack, Nethemba
UsersEditor or administrator accounts you did not create; query the users table directly, because one variant tries to hide its account from the normal user functionNethemba, Patchstack
Access logsPlugin upload and activation requests on the dates in questionSansec

Run these checks from the server or with wp plugin list, which includes the must-use status. If you find something, remove the UpdraftCentral key first. Patchstack's order is to delete the key before the backdoor, otherwise a replacement can be pushed.

The Brevo case is narrower. Brevo says if an administrator was logged in and visited a page embedding its widget on 14 September, check for plugins installed or activated that day.

For the wider picture of this month's incidents, see the UpdraftCentral action list, the October 2026 incident tracker and the small-business summary, or browse the other WordPress guides.

What is the general pattern?

Patchstack describes a key pair generated on each site connection, with commands signed by genuine dashboard private keys that stayed with the vendor's cloud service. Three questions sort the risk:

QuestionIf the answer is yes
Can the connection install code or add users?It is a full-control key. Treat it like an administrator password.
Does the vendor hold the key, not just you?Your update habits do not protect it.
Do you still use the connection?If not, delete it.

This page lists what the sources cover. TeamUpdraft's page was last updated 29 October 2026, and we re-read it on 2 November 2026. UpdraftPlus 1.26.14, released 26 October, is the current version and changes nothing in the steps above.

Questions people ask

Can a plugin vendor access my site?

Only if the plugin gives them a way in. For UpdraftCentral, Nethemba describes a key pair where whoever holds the dashboard's key at the vendor can send commands your site runs.

I never used UpdraftCentral. Can I have a key anyway?

Possibly. Patchstack reported that the option to add the site to UpdraftCentral is pre-ticked when you connect a TeamUpdraft account. Check the UpdraftCentral screen in the plugin settings instead of relying on memory.

I updated the plugin. Do I still need to delete the key?

Check. TeamUpdraft says 1.26.13 and 2.26.13 disconnect every UpdraftCentral connection made before 13:07 BST (12:07 UTC) on 18 October, but Nethemba reports that keys created on 18 October between 12:07 and 21:00 UTC are left in place. Deleting a key also does not remove a backdoor plugin or account that was added earlier.

Is a signed command from my plugin vendor trustworthy?

In UpdraftCentral, Nethemba reports the site cannot tell a real command from a stolen-key command, because both are validly signed. That is why the key list matters more than the plugin version.

How do I know which plugins hold remote-control keys?

Look for any plugin or service whose settings say connect this site to a dashboard, cloud account or remote manager. Write down each one, who holds the other half of the key, and whether you still use it. Remove the connection for anything you do not actively use.

Sources

  1. TeamUpdraft: security incident, October 2026 (vendor page, last updated 29 October 2026)The vendor's account of the breach, the fixed versions and its recommended order of steps. Re-read 2 November 2026.
  2. Patchstack: UpdraftCentral key compromise and WordPress backdoorsIndependent analysis: the pre-ticked connection option, 99 backdoor plugin names, remediation order. Written 19 October, before the fix existed.
  3. Nethemba: UpdraftCentral backdoor analysisHow the signed-command design works, and the 1.26.12 versus 1.26.13 behaviour.
  4. Brevo post-mortem: Cloudflare Worker injection on 14 September 2026Brevo's own notice: timeline, affected domains and scripts, root cause and customer guidance. Checked 24 October 2026.
  5. Sansec: Brevo supply chain attack (16 September 2026)Researchers' timeline, the two payloads, the 100,000 site estimate and the advice to compare plugin files on disk with the admin screen.
  6. Rank Math: PRO 3.0.123 security incidentVendor notice for a download that contained malware, with the download window and recovery steps.
  7. WordPress developer docs: must-use pluginsWhere must-use plugins live and why they are listed separately.
  8. WP-CLI: wp plugin listLists installed plugins, including the must-use status.
  9. WP-CLI: wp option getReads a single database option, as used in Patchstack's key check.
  10. WordPress.org detailed plugin guidelinesGuidelines 7 and 8 on external servers and remotely loaded code.

Facts on this page are dated and point at the primary source next to them. If a vendor status changes after the date shown, the vendor's page wins; tell us at support@run.cloud and we will update it.