Has my WordPress site been hacked?

  • Free, no sign-up
  • Result in a few seconds
  • Sources re-read on 26 October 2026

A domain name is enough. The home page and at most nine small public files are read, as a browser would: nothing is scanned. Only the website address and its result are kept, for statistics.

Your result

Enter your site address to start

The result says whether the site runs on WordPress, which version it shows, whether a plugin is vulnerable or was closed for a flaw, whether a page was slipped in, and what a visitor can see that looks wrong.

Be warned at the next vulnerability

A single e-mail: the vulnerability, whether your site is affected and what to do. Never any advertising.

What I do with your address

Not sure? Send me your site address, and within 24 hours I tell you what I see and what to do. Free, no commitment.

Send my site address How the remote work goes, and its pricesAlso check HTTPS, mobile, e-mails and legal notice: test my website

Rather have me handle it? Check from the inside, clean-up, keys and passwords changed, updates done, written report. Free diagnosis, updates from €190, clean-up on quote, reply within 24 hours.

See the offer and prices 

Website looking dated? Showcase website redesign from €1,500. A clear, fast website, well ranked on Google, built on up-to-date tools and easy to edit yourself. Free fixed-price quote, reply within 24 hours.

Talk about my website redesign 

About this test

Over the weekend of 17 and 18 October 2026, connection keys for UpdraftCentral, the remote management tool of the UpdraftPlus backup plugin, leaked from its publisher. From 18 October, they were used to install fake plugins and hidden accounts on WordPress sites, including up-to-date ones. A hacked site does not always show it: it redirects some visitors, adds hidden links, or waits. This tool reads your home page and a few public files, spots a plugin still below its fixed version, an outdated WordPress or signs of injection, and tells you what to do: nothing, check, or act today.

Portrait of Léo Guillaume, founder of Dibodev

Tool built by Léo Guillaumefreelance developer near Rennes, France. I clean up, update and secure WordPress sites, online stores and business software for small businesses, remotely, and I reply within 24 hours.

Updated on

What happened

UpdraftPlus, UpdraftCentral and the WordPress sites hacked in October 2026, in six facts

UpdraftPlus is the most widely used backup plugin for WordPress. In October 2026, its remote management tool became the way in. Here is what the publisher and the security teams say, without drama.

17-18 October 2026

UpdraftCentral keys leaked from the publisher

TeamUpdraft, the publisher of UpdraftPlus, suffered an intrusion over the weekend of 17 and 18 October 2026. The connection keys of UpdraftCentral, its remote site management tool, were part of it. It is not a flaw in the plugin code: the commands sent to the sites were signed with real keys.

Source: TeamUpdraft, post of 19 October 2026

From 18 October

Fake plugins and hidden accounts

Patchstack saw the first attack on 18 October at 15:32 UTC. The command installs a fake plugin ("Small maintenance toolkit", "Site Health Cache"…), which creates an account able to install plugins and a login through a secret link, with no password and no two-factor authentication. Patchstack recorded 99 different plugin names.

Source: Patchstack, analysis of 19 October 2026

Up-to-date sites too

Being up to date was not enough

The IT-Connect site, on UpdraftPlus Premium 2.26.11, received the command on 19 October at 7:17 am. The way in was a valid key, not an old version: any site linked to UpdraftCentral was exposed, whatever its version.

Source: IT-Connect, 19 October 2026

Ticked by default

A key can exist without you knowing

When you link a site to your TeamUpdraft account, the box that adds it to UpdraftCentral is ticked by default, and these keys do not expire. Nethemba, which discovered the attack, advises deleting the key even after a clean-up, and moving a fake plugin off the site rather than deleting it from the admin, which would wipe its traces.

Source: Nethemba, analysis of 19 October 2026

1.26.13 and 2.26.13

The fixed version, and what it does not do

UpdraftPlus 1.26.13 (2.26.13 for Premium), released on 19 October, revokes the keys created before the incident; 1.26.12, released the same day, did not revoke them because of a bug. Updating stops a new command, but removes neither a fake plugin, nor an account, nor a session already open.

Source: BleepingComputer, 20 October 2026

72 hours

A hack that touches personal data must be reported

If the site holds customer accounts, orders or a form that stores data, an intrusion is a data breach. In France and the rest of the EU, it is reported to the data protection authority (the CNIL in France) within 72 hours when it creates a risk for people, and the people are told when the risk is high.

Source: CNIL, reporting a personal data breach

What I do for you: I read the site from the inside, remove what does not belong there, change the keys and passwords, restore a clean backup if needed, update WordPress, the theme, the plugins and PHP, and write down what was done. Remotely, free diagnosis, quote before any work.

The signs

What a hacked WordPress site looks like

A hack does not aim to break your site: it wants to use it, for as long as possible. Here is what a visitor, the tool or you can notice.

  • Hidden links or pages that do not exist

    Invisible links to betting, pharmacy or counterfeit sites, or hundreds of pages in Japanese in Google under your domain name. This is SEO spam, the most common kind.

  • A redirection for some visitors

    The site looks normal to you, but a visitor coming from Google on a phone lands somewhere else. The tool spots a redirection in the page code; on the inside, it often hides in the .htaccess file or a plugin.

  • A warning from Google or the host

    "Deceptive site ahead" in Chrome, a Search Console message, or a host that suspends the site for sending spam: the hack is already old.

  • .php files where there should be none

    The wp-content/uploads folder only holds images and documents. A .php file inside it, or an unknown folder in wp-content/mu-plugins or wp-content/upgrade, is a backdoor until proven otherwise.

  • An account you did not create

    The fake plugins of October 2026 create an Editor account and give it the right to install plugins, with a name like data-ops43, displayed as "Site Tools", and an @example.org address. Look at the rights of every account, not only the administrators.

  • A critical error on some pages

    The first variant of these fake plugins caused an "Undefined constant" error on uncached pages. Do not fix that code: repairing it would wake the backdoor up. Move the plugin folder off the site instead.

Watch list

The plugins the tool checks, and the version that fixes them

For each plugin on the list, the tool reads the public readme.txt file and compares the installed version with the fixed one. UpdraftPlus and Ninja Forms are always checked, the others when the home page shows them. Paid plugins do not always have a public readme: the result then says "version not readable".

  • UpdraftPlus1.26.13 or later

    UpdraftCentral keys stolen from the publisher, fake plugins installed from 18 October 2026, up-to-date sites included

    2.26.13 for Premium, then delete the UpdraftCentral key

  • Ninja Forms3.15.4 or later

    Unauthenticated XSS (CVE-2026-94504), exploited since 4 October 2026 by a campaign that hides its own admin account

    Current version: 3.15.6

  • WPC Product Bundles for WooCommerce8.6.7 or later

    Unauthenticated XSS (CVE-2026-93836), same campaign as Ninja Forms

    WooCommerce stores

  • Bricksforge3.1.8.10 or later

    Unauthenticated file upload (CVE-2026-85097), exploited since 7 October 2026

    Paid add-on for Bricks

  • Elementor Pro4.2.2 or later

    PHP file upload through forms (CVE-2026-32475), exploited since 19 August 2026

    Paid plugin: read the version in the admin

  • Super Forms6.3.314 or later

    Unauthenticated file upload (CVE-2026-14894), exploited since 14 July 2026

    Paid plugin

  • All-in-One WP Migration7.110 or later

    SQL injection (CVE-2026-19949), fixed on 20 August 2026, no exploitation reported

    More than 5 million sites

Your plugin is not on the list? The tool only checks plugins whose vulnerabilities were exploited or widely reported in recent months. For the others, the WordPress admin flags every plugin that has an update: install them all, and delete the ones you no longer use.

In order

What to do today, in four steps

The same path for a showcase site, a blog or a WooCommerce store. Allow an hour if the site is healthy, more if it has been hacked.

  1. Back up

    A full copy, off the server, before anything else

    Files and database, downloaded to your computer or sent to external storage. Even hacked, this copy is evidence and helps find what was changed. Restore nothing before you have finished looking.

  2. Check

    Accounts, plugins, files, UpdraftCentral key

    The accounts that can install plugins, not only administrators. The plugins including the "Must-Use" tab, and the wp-content/mu-plugins and wp-content/upgrade folders. The .php files in wp-content/uploads. The UpdraftCentral key and Search Console. The "checks to do today" guide gives the order and the places.

  3. Clean

    Remove, change, restore

    Move the fake plugins off the site rather than deleting them from the admin, delete the unknown accounts, change every password and the secret keys, delete the UpdraftCentral key. If doubt remains, restore a backup from before 17 October, then repeat these steps: that is the restore guide.

  4. Close the door

    Updates, PHP, and a monthly routine

    WordPress, theme and plugins up to date, unused plugins deleted, a fixed PHP version at the host, one off-server backup a week. Only reconnect UpdraftCentral once the publisher has finished its investigation. And if personal data may have leaked, report it within 72 hours.

Frequently asked questions

Your questions about a hacked WordPress site

How do I know if my WordPress site has been hacked?

From outside: this tool, a "site:yourdomain.com" search in Google to spot pages you did not write, and a visit from a phone in private browsing to catch a redirection. From the inside: the accounts that can install plugins, the list of plugins with the "Must-Use" tab, the recently modified files and the access logs of your host. The "checks to do today" guide details each point.

My site is up to date, and so is UpdraftPlus: am I still affected?

Yes, if the site had an active UpdraftCentral key. The way in was a valid key, not an old version, and the box that creates this key is ticked by default when you link a site to your TeamUpdraft account. Update to 1.26.13 (2.26.13 for Premium), delete the key in the UpdraftPlus advanced tools, then check the accounts, plugins and files: the update alone removes nothing that was already installed.

What should I do first if my site has been hacked?

A full copy off the server, then a change of every password (WordPress, FTP, database, hosting account, linked email) and of the secret keys in wp-config.php. Only then the clean-up: unknown accounts and plugins, recent files, redirections. If you cannot do it yourself, put the site in maintenance at your host and write to me.

Do I need to change my passwords?

Yes, all of them, as soon as there is a doubt, and a second time after the clean-up: WordPress (every administrator), FTP or SFTP, database, hosting account, TeamUpdraft account, and the email address that receives password resets. Change the secret keys in wp-config.php too: they close every open session, the attacker’s included.

My site has shown a critical error for a few days: is it related?

Maybe. A critical error often has a mundane cause, such as a PHP update or an incompatible plugin. But the first variant of the fake plugins of October 2026 caused an "Undefined constant" error on uncached pages. If the message names a plugin you do not know, do not fix its code: move its folder off the site and follow the checks guide.

My host says the site sends spam, or has suspended it: what should I do?

It is almost always a hack. Ask the host for the files or scripts involved and the logs, make the copy, then clean up or restore an earlier version. The site should only come back online once the passwords are changed and the updates done, or it may be suspended again.

Is restoring a backup enough?

Only if the backup predates the intrusion, so before 17 October for UpdraftCentral, and if you close the door right after. A backup from that date may still hold the old UpdraftCentral key: delete it again, change the passwords and secret keys, and update everything. The restore guide explains how to pick the right backup.

Would Wordfence, Sucuri or a security plugin have prevented this?

They help detect (modified files, suspicious logins) and block part of the attacks, but a command signed with a real key looks legitimate. They replace neither updates, nor deleting unused plugins, nor unique passwords with two-factor authentication.

Does my host take care of this?

The host maintains the server and the PHP version, not your WordPress, your plugins or your accounts. It can suspend a site that sends spam and give you the logs. The clean-up stays with you or your provider.

Do I need to tell my customers or the data protection authority?

If the site keeps personal data (accounts, orders, stored forms) and an intrusion may have reached it, it is a data breach: in the EU, it is reported to the authority within 72 hours as soon as there is a risk for people, the people are told if the risk is high, and it is recorded in writing in all cases. A showcase site that stores no data has nothing to report.

What exactly does this tool do, and what can it not see?

It reads the home page once, as a browser would, then at most nine small public files: the RSS feed when the page hides its version, the readme.txt of the watched plugins, the public list of authors and the twenty latest published pages and posts. It also asks WordPress.org whether a plugin seen on the page was closed for a flaw. It recognises WordPress, its version when shown, a listed plugin below its fixed version, a page slipped in (links to casinos or pharmacies, text in a language foreign to the site, backdating), hidden links, a redirection, an encoded script, spam words, .php files in the uploads and a critical error. It scans nothing, sends no payload and keeps the result ten minutes in cache, no more. It cannot see a fake plugin that loads nothing on the page, nor a hack that only targets some visitors: only a check from the inside settles it.

Blog

Going further

The three guides of this page, the article on the October 2026 PHP vulnerability, and a read to take back control of a site nobody looks after anymore.

Need someone to take care of it?

Send me the site address. I check from the inside, clean up, change the keys, update everything and write down what was done. Free diagnosis within 24 hours, quote before any work.