A Flaw in a WordPress Backup Plugin Lets Strangers Switch On Plugins You Left Switched Off — Check Yours Today
November 17, 2026 | Zain Ali | 5 min read
A security flaw has been found in Everest Backup, a WordPress plugin for backing up, migrating, restoring and cloning websites, and it lets a stranger switch on plugins on your site without logging in. The vulnerability was published in the official CVE record on Tuesday 17 November 2026, with the details coming from security firm Wordfence. The fix is already out in version 2.3.15, which was released on 11 November — so if your site has not updated since then, it is still exposed.
Everest Backup is the kind of plugin many small business sites run quietly in the background: it takes backups, moves a site to a new host, or clones it for testing. That is exactly why a flaw in it matters. A backup plugin sits at the heart of a site, and a weakness in it can hand a stranger control over parts of the site they should never reach.
What the flaw does
The vulnerability is tracked as CVE-2026-97639 and carries a severity score of 5.3 out of 10, which Wordfence rates as medium. The plugin failed to check that the person asking it to switch on an add-on was allowed to do so. In plain terms, anyone on the internet could send a request that activates a plugin already installed on the site but switched off — no account on the website, and no login, required.
That limit matters: the attacker cannot install a new plugin, only switch on ones that are already there. But that is still a real problem, because most WordPress sites accumulate switched-off plugins over time — an old contact form, a gallery tried once, a booking tool that was replaced. Site owners leave them installed because they feel harmless while they are off. This flaw shows they are not. An old plugin that was switched off years ago may itself have known security holes, and once it is switched back on, those holes are live again.
The flaw affects every version of Everest Backup up to and including 2.3.14. Version 2.3.15 fixes it by adding the checks that were missing: the person asking to switch something on must now be logged in, must have permission to activate plugins, and the request must carry a valid security token. No exploitation of this flaw has been reported so far, and it does not appear on the US cybersecurity agency CISA’s list of vulnerabilities known to be exploited — but the details are now public, and that is usually the point at which attackers start trying.
What this means for your business
If your website runs WordPress, work through these checks today. The update itself is a one-click plugin update, and the rest takes a few minutes.
- Check whether you have Everest Backup, and which version. In your WordPress dashboard, go to Plugins and look for Everest Backup. If it shows 2.3.14 or earlier, update it to 2.3.15 or later.
- Back up first. Take a backup of the site before updating, using whatever backup routine you already have, so you can roll back if anything goes wrong.
- Audit your switched-off plugins — this is the wider lesson. Still on the Plugins screen, look at the inactive list. If there is a plugin you no longer use, delete it rather than leaving it sitting there. A deactivated plugin is not a harmless plugin: it is code on your server, waiting to be switched back on.
- After updating, check your active plugin list for anything you do not recognise. If a plugin you left switched off is suddenly active, switch it off again and delete it if you do not need it. An unexpected change here is a sign someone has been in.
- If anything looks wrong, act on it before doing anything else. Change your WordPress administrator passwords, and get help checking the site properly. Installing the update closes the hole, but it does not undo changes an attacker has already made.
It is also worth remembering that a backup plugin is one of the most trusted pieces of software on a site: it holds copies of everything, and it is expected to run without being noticed. That trust is exactly why it should be kept updated like everything else, and why the plugins sitting unused beside it deserve the same attention.
A word from Zain Ali
“A switched-off plugin feels safe, but this flaw shows it is only one missing check away from being switched back on,” said Zain Ali, founder of Zee Developers. “If you use Everest Backup, update it to 2.3.15 today, and while you are in there, delete the plugins you no longer use — they are not doing your site any good sitting there. Five minutes now is a lot cheaper than finding out an old plugin has been turned back on.”
If you would like us to check whether your website is affected and apply the update for you, get in touch and we will take a look.
Sources: Wordfence Threat Intelligence advisory for CVE-2026-97639; CVE record for CVE-2026-97639, published 17 November 2026.