BackWPup vulnerability history, read beside its jobs, destinations and logs
One BackWPup job can store the same backup on several destinations at once, and every run leaves a log.
Here are its vulnerability records, with the screens that show where copies go, which panel holds a login and who can download or restore one.
On this page
BackWPup vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 16 records for BackWPup. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 5.7.7
Worked out from data retrieved on .
Every affected range listed in this source for BackWPup ends before version 5.7.7.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
BackWPup - WordPress Backup & Restore Plugin < 5.7.7 - Unauthenticated Information Exposure
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2026-86826
Affected versions- All versions before 5.7.7
Patched versions: 5.7.7
Update to at least version 5.7.7.
BackWPup - WordPress Backup & Restore Plugin 3.3 - 5.7.6 - Missing Authorization
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2026-86827
Affected versions- From version 3.3 up to and including 5.7.6
Patched versions: 5.7.7
Update to at least version 5.7.7.
BackWPup - WordPress Backup & Restore Plugin < 5.7.7 - Authenticated (Administrator+) Path Traversal
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.9)
- CVE:
- CVE-2026-86828
Affected versions- All versions before 5.7.7
Patched versions: 5.7.7
Update to at least version 5.7.7.
BackWPup - WordPress Backup & Restore Plugin 5.2.2 - 5.7.4 - Missing Authorization
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.3)
- CVE:
- CVE-2026-86815
Affected versions- From version 5.2.2 up to and including 5.7.4
Patched versions: 5.7.5
Update to at least version 5.7.5.
BackWPup <= 5.7.4 - Unauthenticated Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
- CVE:
- CVE-2026-65443
Affected versions- All versions up to and including 5.7.4
Patched versions: 5.7.5
Update to at least version 5.7.5.
Show 11 older recordsHide the older records
BackWPup <= 5.6.6 - Authenticated (Administrator+) Local File Inclusion via 'block_name' Parameter
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
- CVE:
- CVE-2026-6227
Affected versions- All versions up to and including 5.6.6
Patched versions: 5.6.7
Update to at least version 5.6.7.
BackWPup 5.0.0 - 5.6.2 - Authenticated (BackWPup Helper+) Privilege Escalation via Arbitrary Options Update
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
- CVE:
- CVE-2025-15041
Affected versions- From version 5.0.0 up to and including 5.6.2
Patched versions: 5.6.3
Update to at least version 5.6.3.
BackWPup 5 - 5.5.0 - Missing Authorization to Sensitive Information Exposure
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2025-10579
Affected versions- From version 5 up to and including 5.5.0
Patched versions: 5.5.1
Update to at least version 5.5.1.
BackWPup <= 4.0.1 - Authenticated (Administrator+) Directory Traversal
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.8)
- CVE:
- CVE-2023-5505
Affected versions- All versions up to and including 4.0.1
Patched versions: 4.0.2
Update to at least version 4.0.2.
BackWPup <= 4.0.2 - Plaintext Storage of Backup Destination Password
- Published:
- Last updated:
- Severity:
- Low (CVSS 2.2)
- CVE:
- CVE-2023-5775
Affected versions- All versions up to and including 4.0.2
Patched versions: 4.0.3
Update to at least version 4.0.3.
BackWPup <= 4.0.3 - Sensitive Information Exposure
- Published:
- Last updated:
- Severity:
- High (CVSS 7.5)
- CVE:
- CVE-2023-7164
Affected versions- All versions up to and including 4.0.3
Patched versions: 4.0.4
Update to at least version 4.0.4.
BackWPup <= 4.0.1 - Authenticated (Administrator+) Directory Traversal
- Published:
- Last updated:
- Severity:
- High (CVSS 8.7)
- CVE:
- CVE-2023-5504
Affected versions- All versions up to and including 4.0.1
Patched versions: 4.0.2
Update to at least version 4.0.2.
BackWPup <= 3.4.1 - Unauthenticated Backup Download
- Published:
- Last updated:
- Severity:
- High (CVSS 7.5)
- CVE:
- CVE-2017-2551
Affected versions- All versions before 3.4.2
Patched versions: 3.4.2
Update to at least version 3.4.2.
BackWPup < 3.0.13 - Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2013-4626
Affected versions- All versions before 3.0.13
Patched versions: 3.0.13
Update to at least version 3.0.13.
BackWPup <= 1.7.1 - Remote File Inclusion
- Published:
- Last updated:
- Severity:
- Critical (CVSS 9.8)
- CVE:
- CVE-2011-4342
Affected versions- All versions up to and including 1.7.1
Patched versions: 1.7.2
Update to at least version 1.7.2.
BackWPup - WordPress Backup Plugin < 1.4.1 - Directory Traversal
- Published:
- Last updated:
- Severity:
- High (CVSS 7.5)
- CVE:
- CVE-2011-5208
Affected versions- All versions before 1.4.1
Patched versions: 1.4.1
Update to at least version 1.4.1.
Check BackWPup on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
What BackWPup backs up, and how a job gets started
BackWPup is a backup and restore plugin that its WordPress.org listing shows as By WP Media.
The listing says it backs up your database and files, stores them on your server or in the cloud, and lets a single backup job store the same backup across multiple destinations at once.
Settings reach it through job cards in the dashboard, and files through restore, which the listing says the free version offers for backups you upload. A job can also start outside the dashboard. The listing gives Free and Pro WP-CLI support and, starting with version 5.7, AI assistants that run backups through MCP.
The vendor's scheduling guide adds a Frequency choice, Triggered by link, whose URL will immediately start the job when visited in a browser or hit by an external cron job.
Access wording in the history's titles includes Unauthenticated, Authenticated (Administrator+) and, on CVE-2025-15041, Authenticated (BackWPup Helper+). The listing's changelog mentions BackWPup user roles in its 3.9.0 entry.
BackWPup vulnerabilities on record, and how to read their ranges
Missing Authorization ends more than one title in this history, and Information Exposure, Directory Traversal and Cross-Site Scripting each recur.
- CVE-2026-86827, whose title ends "Missing Authorization", covers from version 3.3 up to and including 5.7.6 and lists 5.7.7 in its patched versions field.
- CVE-2025-15041, whose title ends "Authenticated (BackWPup Helper+) Privilege Escalation via Arbitrary Options Update", covers from version 5.0.0 up to and including 5.6.2 and lists 5.6.3.
- CVE-2023-5775, whose title ends "Plaintext Storage of Backup Destination Password", covers all versions up to and including 4.0.2 and lists 4.0.3.
- CVE-2017-2551, whose title ends "Unauthenticated Backup Download", covers all versions before 3.4.2 and lists 3.4.2.
Ranges that begin partway
Not every range reaches back to the first release: CVE-2026-86827 begins at version 3.3 and CVE-2025-15041 at 5.0.0. A copy older than 3.3 sits outside the first of those and inside CVE-2017-2551. So set the installed version against every affected range in the history.
One title, two CVE ids
CVE-2023-5504 and CVE-2023-5505 carry one title, "BackWPup <= 4.0.1 - Authenticated (Administrator+) Directory Traversal", and the same affected range and patched versions field: all versions up to and including 4.0.1, with 4.0.2 listed as patched. Each has its own published date and severity, so put the CVE id in a ticket, not the title.
Reading BackWPup's job cards, storage panels and logs without running anything
These checks are for a site you have permission to review, and each stops at reading.
The vendor's scheduling guide puts a Backup Now button at the top right of the BackWPup settings page, which creates a full backup, and a small backup icon on each job card, which runs that job. Press neither. The listing's install steps have a new user open BackWPup and follow a guided setup: if one appears where you expected the dashboard, stop and ask the site owner.
WordPress prints each plugin's version number in the Description column of the Plugins screen. Write it down for every row named BackWPup, including any under the Inactive link: the vendor's install guide has Pro uploaded as a zip file of its own, and the changelog's 5.2.3 entry reads "Fixed fatal error when both Free and Pro versions are activated together".
The scheduling guide finds jobs in the Next Scheduled Backups section of the dashboard, each on a card with a Frequency option offering hourly, daily, weekly or monthly runs. Clicking Frequency is how the guide adjusts a schedule, so close whatever it opens without saving.
For each card, write down the job's title, whether it covers files, the database or both, its frequency and its storage. Where the frequency reads Triggered by link, the guide says the URL is displayed with a copy button: record that the job is link-triggered and ask who was given the link, but do not open it or paste it into your notes.
The changelog's 5.1.3 entry adds a filter to show legacy/disabled jobs, so list those too, with any link they carry.
The vendor's FTP guide gives these as steps for configuring a new FTP destination: the Storage option on a job card opens a Storage Settings sidebar, and selecting FTP there opens a panel with FTP Server & Port, Username & Password, Timeout, a tick box for an explicit SSL-FTP connection, FTP passive mode, Folder to store files in and Max backups to retain.
Open a panel only for a destination the job already uses, and close it without saving. Write down the server, the username, the folder, whether the SSL box is ticked and the retention number, where the guide says 0 keeps all backups indefinitely. Keep the password out of your notes and leave Save & Test connection alone.
For Website Server, the vendor's folder guide has a path for the folder where backups are stored, typically within the wp-content directory, and its own Max backups to retain field. For every other destination, note whose account it connects to.
The vendor's two log articles give different paths. The log settings article goes to BackWPup > Settings > Advanced Settings > Logs and then Access to Logs; the article on viewing a job's log goes to BackWPUp > Settings > Advanced Settings > Jobs > Access to Logs.
By the second, hovering over a name in the table displays links to view, delete or download the log file. Use view only.
Among the Logs settings, write down the Log File Folder and the address under Send Log to Email Address. The settings article says the folder can be an absolute path or a path relative to the wp-content folder, while the changelog's 4.0.2 entry reads "Disallow backups or logs directories from being outside of wp-content directory for security purposes".
Its 5.6.10 entry added backup path visibility in logs. So a log, and the mailbox it is sent to, may show where an archive sits.
The vendor's download article places a Backups History section on the settings page, listing existing backups with details such as Created at, Type, Stored on and Data. Write those down for every row. A row's three dots reveal View log, Download, Restore Backup and Delete.
By the article, Download saves a copy of the backup to your local device, Restore Backup reverts your site to the state at the time of the backup, and Delete removes the backup file from the storage destination. Choose none of the three.
Then list who may be able to reach that menu. WordPress's Users screen has a filter link for each role above its table: start with every Administrator and every holder of a role whose name begins with BackWPup. Add anyone with shell access: the listing has both editions supporting WP-CLI.
Where a Website Server folder sits inside the web root, sign out, request the folder's address with no file name and record the status code. Request no archive.
What a version number leaves out of BackWPup security
A version inside an affected range shows that a known record covers the installed copy of BackWPup.
It does not show whether anyone used the flaw, who holds a job's trigger link, or where older archives now sit.
Nor does a version show code that changes the plugin from outside its screens. The changelog's 4.1.3 entry says the plugin protects your folders by default and that a filter, backwpup_protect_folders, can disable this, while its 5.6.3 entry reads "Re-enabled automatic folder protection to prevent backup directories from being publicly accessible".
Search the site's code for that filter, and for backwpup_disable_ftp_server_ssl, which the FTP guide warns disables SSL security for the FTP transfer.
A WordPress security audit looks for backup archives and copies of wp-config.php left in the web root, checks for directory listings, and lists which accounts hold an application password, the credential the vendor's MCP guide asks for before an AI assistant is connected.
Frequently asked questions
Go by the affected range and patched versions field on each record, not its title. CVE-2026-86827 runs from version 3.3 up to and including 5.7.6 and lists 5.7.7, while CVE-2023-5775 covers all versions up to and including 4.0.2 and lists 4.0.3. A copy can sit outside one and inside the other, so check each range in turn.
Take the installed version from the WordPress Plugins screen and set it beside the update guidance at the top of the history. The changelog on the plugin's WordPress.org listing labels lines Security fix, and its 5.6.3 entry names CVE-2025-15041: read it as a second place to check before an update. On BackWPup Pro, which the vendor's install guide uploads as a zip file, do not wait for a notice: WordPress says a plugin installed from a ZIP file shows one only if its author includes a built-in updater, and the changelog's 5.6.4 entry reads "Fix: Plugin update mechanism not working properly for Pro version since 5.6.2".
The records are those the source data files under the slug backwpup, and being filed there does not settle whether one applies to the paid edition. On how the editions install, the vendor's guide says the Pro zip file comes from your BackWPup account and is uploaded under Plugins > Add new or sent by FTP to the /wp-content/plugins folder. The listing's changelog marks some lines (pro), so on a Pro site read it against that row's version.
By the listing, starting with version 5.7, assistants connected through MCP can check backup status, run backups and review logs. The vendor's MCP guide says the connection takes your WordPress username and an Application Password generated from your WordPress profile. WordPress lets existing application passwords be viewed on the Edit User page, so list them for every account that can open BackWPup. The changelog's 5.7.7 entry adds an OAuth sign-in option for connecting assistants, so ask which were connected that way, and its 5.7.3 entry adds a filter, backwpup_mcp_server_enabled, to allow disabling MCP. Its 5.7.8 entry adds a notice guiding MCP users to install the standalone MCP Adapter plugin, "which is no longer bundled with BackWPup", so look for that plugin's row too.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to every record listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Source records
- BackWPup - WordPress Backup & Restore Plugin < 5.7.7 - Unauthenticated Information Exposure (CVE-2026-86826)
- BackWPup - WordPress Backup & Restore Plugin 3.3 - 5.7.6 - Missing Authorization (CVE-2026-86827)
- BackWPup - WordPress Backup & Restore Plugin < 5.7.7 - Authenticated (Administrator+) Path Traversal (CVE-2026-86828)
- BackWPup - WordPress Backup & Restore Plugin 5.2.2 - 5.7.4 - Missing Authorization (CVE-2026-86815)
- BackWPup <= 5.7.4 - Unauthenticated Stored Cross-Site Scripting (CVE-2026-65443)
- BackWPup <= 5.6.6 - Authenticated (Administrator+) Local File Inclusion via 'block_name' Parameter (CVE-2026-6227)
- BackWPup 5.0.0 - 5.6.2 - Authenticated (BackWPup Helper+) Privilege Escalation via Arbitrary Options Update (CVE-2025-15041)
- BackWPup 5 - 5.5.0 - Missing Authorization to Sensitive Information Exposure (CVE-2025-10579)
- BackWPup <= 4.0.1 - Authenticated (Administrator+) Directory Traversal (CVE-2023-5505)
- BackWPup <= 4.0.2 - Plaintext Storage of Backup Destination Password (CVE-2023-5775)
- BackWPup <= 4.0.3 - Sensitive Information Exposure (CVE-2023-7164)
- BackWPup <= 4.0.1 - Authenticated (Administrator+) Directory Traversal (CVE-2023-5504)
- BackWPup <= 3.4.1 - Unauthenticated Backup Download (CVE-2017-2551)
- BackWPup < 3.0.13 - Cross-Site Scripting (CVE-2013-4626)
- BackWPup <= 1.7.1 - Remote File Inclusion (CVE-2011-4342)
- BackWPup - WordPress Backup Plugin < 1.4.1 - Directory Traversal (CVE-2011-5208)