---
title: "Backup and Security Plugin Vulnerabilities: 35 Flaws Triaged"
slug: "backup-and-security-plugin-vulnerabilities-triage"
description: "We triaged 35 backup and security plugin vulnerabilities from the last four months. Twelve need no login, 15 need an admin account, and all eight plugins are patched."
date: 2026-11-14
author: "WP Vanguard Team"
category: "Research"
palette: "roundup"
tags: ["backup-and-security-plugin-vulnerabilities", "backup-plugin-security", "security-plugin-vulnerability", "cve-2026-19718", "unauthenticated-vulnerability"]
featured_image: "/images/blog/backup-and-security-plugin-vulnerabilities-triage.jpg"
---

Our database holds 35 vulnerabilities in eight backup and security plugins, published between mid-July and 13 November, and only 12 of them can be triggered without logging in. Fifteen need an administrator account, three need a Subscriber or custom role, and five don't say in their titles. Together the eight plugins run on about 14.5 million sites, and every one of them has a fixed release out.

That split is the useful part. A list of 35 CVEs reads like an emergency. Sorted by who can trigger them, it's a short job for most sites and a real one for a few. This post sorts them, names the 12 that matter most, and shows what to check first. We already covered one slice, the [backup plugins whose payload waits for a migration](/blog/wordpress-backup-plugin-vulnerability), so this is the wider view across backup and security plugins.

```bars
{"title": "35 backup and security plugin CVEs by what the attacker needs", "highlight": "No login", "note": "Classified from the advisory titles. WP Vanguard database, July 15 to November 13, 2026.", "data": [
  {"label": "No login", "value": 12},
  {"label": "Admin account", "value": 15},
  {"label": "Subscriber or custom role", "value": 3},
  {"label": "Not stated in title", "value": 5}
]}
```

## How we counted

We pulled every row for eight plugins from the vulnerability database (which mirrors the Wordfence feed) with a publish date from 15 July to 13 November. The first one landed on 27 July. The plugins are All-in-One WP Migration, UpdraftPlus, Really Simple Security, Duplicator, WPvivid, BackWPup, BlogVault (which also ships as MalCare and WP Remote) and Backup Migration.

Then we read the privilege level out of each advisory title. Wordfence writes it in plain words: "Unauthenticated", "Administrator+", "Subscriber+". Five titles don't, such as "Missing Authorization" or "Reflected Cross-Site Scripting", and we've left those as their own group instead of guessing. We didn't read all 35 advisories or test any exploit, so treat the groups as a sort order, not a verdict on each bug.

For each plugin we checked the current version and install count on the WordPress directory on 13 November, and compared the current version to the newest fixed version in the database.

## Plugin by plugin

| Plugin | Installs | CVEs | No login | Worst score | Newest fix | Current |
|---|---|---|---|---|---|---|
| All-in-One WP Migration | 5,000,000 | 4 | 2 | 8.8 | 7.111 | 7.113 |
| UpdraftPlus | 4,000,000 | 2 | 0 | 4.3 | 1.26.8 | 1.26.14 |
| Really Simple Security | 3,000,000 | 6 | 4 | 8.8 | 9.8.3 | 9.8.4 |
| Duplicator | 1,000,000 | 5 | 2 | 8.8 | 5.1.0 | 5.1.1 |
| WPvivid | 900,000 | 10 | 1 | 7.5 | 0.9.138 | 0.9.140 |
| BackWPup | 400,000 | 5 | 2 | 7.2 | 5.7.7 | 5.7.8 |
| BlogVault | 80,000 | 1 | 1 | 9.8 | 6.65 | 6.83 |
| Backup Migration | 80,000 | 2 | 0 | 7.2 | 2.1.7 | 2.1.9 |

WPvivid has the most entries by a wide margin, but nine of its ten need an administrator, so its count overstates the risk. BlogVault has one entry, and it's the highest score in the set. Count alone is a poor guide to which plugin to worry about.

Duplicator's row includes Duplicator Pro, which Wordfence files under the same plugin. If you run the Pro edition, check its version separately.

## The 12 that need no login

These are the ones to check first, because an attacker doesn't need an account on your site.

| Plugin | CVE | What it is | Score | Fixed in |
|---|---|---|---|---|
| BlogVault | CVE-2026-19718 | Site takeover via brute force | 9.8 | 6.65 |
| All-in-One WP Migration | CVE-2026-19949 | Second-order SQL injection to code execution | 8.8 | 7.110 |
| Duplicator | CVE-2026-82814 | PHP object injection | 8.8 | 5.0.0 |
| WPvivid | CVE-2026-19725 | Path traversal | 7.5 | 0.9.131 |
| Really Simple Security | CVE-2026-84775 | Denial of service | 7.5 | 9.8.1 |
| BackWPup | CVE-2026-65443 | Stored cross-site scripting | 7.2 | 5.7.5 |
| Really Simple Security | CVE-2026-84777 | Two-factor authentication bypass | 5.3 | 9.8.1 |
| Really Simple Security | CVE-2026-89080 | Two-factor authentication bypass | 5.3 | 9.8.1 |
| Really Simple Security | CVE-2026-88798 | Unbounded option growth | 5.3 | 9.8.3 |
| All-in-One WP Migration | CVE-2026-89064 | Credential exposure via a Basic auth header | 5.3 | 7.111 |
| BackWPup | CVE-2026-86826 | Information exposure | 5.3 | 5.7.7 |
| Duplicator | CVE-2026-112244 | Full path disclosure | 5.3 | 5.1.0 |

The first three at the top are the ones where the score and the install base both argue for updating today. The All-in-One WP Migration and Duplicator entries are the migration-time flaws we wrote up in the earlier post, where the attacker plants something and waits for an admin to restore or migrate.

The BlogVault entry is the one we'd single out. The title says a visitor can take over a site by brute force, which is a 9.8, but the plugin has only 80,000 installs, so it rarely makes a headline. The fix landed in 6.65 and the current release is 6.83. We haven't read the patch, so we can't say what the brute force targets.

> [!KEY]
> Sort a plugin's CVE list by privilege before you decide how urgent it is. Twelve of these 35 need no login. The other 23 need an account, and 15 of those need an administrator.

## When a security plugin is the weak point

Really Simple Security has six entries, four of them without a login, in about two weeks: 2 to 14 September. Three involve the second factor. Two are titled "Unauthenticated Two-Factor Authentication Bypass" (CVE-2026-84777 and CVE-2026-89080, both fixed in 9.8.1), and a third is a missing authorization check that also bypasses 2FA (CVE-2026-82519, fixed in 9.8.2).

A 2FA bypass is serious in a narrow way. It removes the second step of a login, so we'd expect it to matter once an attacker already has or can guess a password, but we haven't read the patches, so that's an expectation, not a finding. Our bigger point is about trust. A security plugin sits in front of your login page, and a flaw there weakens the thing you installed it to strengthen.

The same plugin also had an 8.8 remote code execution flaw (CVE-2026-81766) that needs a custom role, fixed in 9.8.0 on 31 August. Sites that give custom roles to contributors or customers should check that one specifically, which is why [subscriber-level flaws on sites with open registration](/blog/subscriber-level-vulnerability-open-registration) deserve more attention than their label suggests.

## The 15 that need an administrator

Fifteen entries need an administrator account, and ten of them score 7.2 or below on arbitrary file upload, remote code execution, SQL injection and path traversal. WPvivid alone accounts for nine. The same list includes Duplicator CVE-2026-115251, an arbitrary code execution flaw (7.2) reachable by a multisite subsite administrator.

These are lower priority, not ignorable. An administrator-only bug matters when someone other than you holds an admin login, when an admin account gets phished, or on a multisite network where subsite admins aren't fully trusted. On a one-owner site with strong passwords and 2FA, they can wait for the normal update cycle.

## What to do this week

Work through this in order.

1. Check the version of each plugin in the table against the "Current" column. Every plugin in this set has a release at or above its newest fix, so for all of them the action is the same: update. In WP-CLI, `wp plugin list --fields=name,version,update` shows what's behind.
2. Update the 12 no-login plugins first: BlogVault (and MalCare or WP Remote if you use them), All-in-One WP Migration, Duplicator, WPvivid, Really Simple Security and BackWPup.
3. If you run Really Simple Security, confirm you're on 9.8.3 or later and that two-factor login still works after the update.
4. Give custom roles a second look on any site running Really Simple Security before 9.8.0.
5. Review who holds an administrator account. Fifteen of these flaws only matter if someone untrusted has one.

Our guide to [checking plugins for known vulnerabilities](/blog/check-wordpress-plugins-for-known-vulnerabilities) covers doing this across many sites at once, and the [WordPress security checklist](/blog/wordpress-security-checklist) covers the account and permission side. For this week's wider picture, see the [weekly patch list](/blog/wordpress-plugins-to-patch-this-week).

## What we can't tell you

Privilege levels come from advisory titles, so a title that understates what an attacker needs would skew the groups. Five entries have no level in the title and we haven't classified them. The database mirrors the Wordfence feed and can lag a vendor's release, so a fixed version listed here is the newest we recorded, not necessarily the first. And a patched plugin isn't proof a site was never hit. If you ran an unpatched version of any of the 12, look at your [signs of a hacked site](/blog/signs-wordpress-site-hacked) before assuming it's clean.

## Run a scan

[Run a scan on your site](/#scanner) to compare every installed plugin version against our database, including all 35 entries above.

## References

- [Wordfence Intelligence: CVE-2026-19718, BlogVault site takeover](https://www.wordfence.com/threat-intel/vulnerabilities/id/01f287b6-1720-4ece-9141-f906835b8bae)
- [Wordfence Intelligence: CVE-2026-19949, All-in-One WP Migration second-order SQL injection](https://www.wordfence.com/threat-intel/vulnerabilities/id/22e273d9-a268-4dc5-b1f6-3bc5c29232c5)
- [Wordfence Intelligence: CVE-2026-82814, Duplicator PHP object injection](https://www.wordfence.com/threat-intel/vulnerabilities/id/767fb03a-58a3-464b-98b2-5378cfec09ae)
- [Wordfence Intelligence: CVE-2026-19725, WPvivid path traversal](https://www.wordfence.com/threat-intel/vulnerabilities/id/f3f1e629-fe60-4793-b9f1-c02a7a2542aa)
- [Wordfence Intelligence: CVE-2026-84775, Really Simple Security denial of service](https://www.wordfence.com/threat-intel/vulnerabilities/id/eeea5b13-54e8-4482-bdbc-6922cf96b4e1)
- [Wordfence Intelligence: CVE-2026-65443, BackWPup stored cross-site scripting](https://www.wordfence.com/threat-intel/vulnerabilities/id/2dfd592b-cbe9-460a-8b9a-148058d1bd58)
