HomeWordPress vulnerabilitiesAll-in-One WP Migration and Backup
All-in-One WP Migration and Backup vulnerabilities
All-in-One WP Migration and Backup has 11 known vulnerabilities in this database. The most recent published record is dated 18 Sep 2026.
- Known vulnerabilities
- 11
- Active installs
- 5m+
- Latest version
- 7.111
- Last updated
- 15 Sep 2026
- Most recent
- 18 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Privilege escalation CVE-2026-81810 | High 7.2 | Before 7.111 | Fixed in 7.111 | 18 Sep 2026 |
| Security weakness CVE-2026-89064 | Medium 5.3 | Up to 7.110 | Fixed in a later version (latest 7.111) | 17 Sep 2026 |
| SQL injection CVE-2026-19949 | High 8.8 | Up to 7.109 | Fixed in a later version (latest 7.111) | 25 Aug 2026 |
| Privilege escalation CVE-2026-17533 | High 7.2 | Before 7.108 | Fixed in 7.108 | 16 Aug 2026 |
| Path traversal CVE-2026-12898 | Medium 6.5 | Before 7.106 | Fixed in 7.106 | 20 Jul 2026 |
| Cross-site scripting (XSS) CVE-2025-8490 | Medium 4.4 | Up to 7.97 | Fixed in a later version (latest 7.111) | 27 Aug 2025 |
| PHP object injection CVE-2024-10942 | High 7.5 | Up to 7.89 | Fixed in a later version (latest 7.111) | 13 Mar 2025 |
| Remote code execution CVE-2024-9162 | High 7.2 | Up to 7.86 | Fixed in a later version (latest 7.111) | 28 Oct 2024 |
| Sensitive data exposure CVE-2024-8852 | Medium 5.3 | Before 7.87 | Fixed in 7.87 | 22 Oct 2024 |
| Security weakness CVE-2022-2546 | Medium 4.7 | Before 7.63 | Fixed in 7.63 | 2 Feb 2023 |
| Arbitrary file deletion CVE-2022-1476 | Medium 6.6 | Up to 7.58 | Fixed in a later version (latest 7.111) | 10 May 2022 |
Read the published descriptions
- CVE-2026-81810, 18 Sep 2026
- The All-in-One WP Migration and Backup WordPress plugin before 7.111 does not perform any capability check on several of its AJAX actions, gating them only on an installation-wide secret which it discloses to any user permitted to export the site, allowing such a user to import an arbitrary site archive and gain administrator access. Exploitation requires an administrator to have granted the export capability to a role that does not hold the All-in-One WP Migration and Backup WordPress plugin before 7.111's own import capability, which is not a default configuration. CVE record
- CVE-2026-89064, 17 Sep 2026
- The All-in-One WP Migration and Backup plugin for WordPress is vulnerable to Insufficient Credential Protection in versions up to, and including, 7.110. This is due to the `Ai1wm_Main_Controller::init()` method - registered on the `admin_init` hook, which fires unauthenticated on `admin-ajax.php` and `admin-post.php` requests - reading `$_SERVER['PHP_AUTH_USER']` and `$_SERVER['PHP_AUTH_PW']` from any incoming request and writing them to the `ai1wm_auth_header` option via `update_option()` as a reversible base64-encoded string, with no capability check, nonce verification, `is_user_logged_in()` check, or confirmation that Basic authentication actually succeeded. This makes it possible for unauthenticated attackers to capture into the database, in reversible base64 form, any WordPress Application Password or HTTP Basic credential presented to `/wp-admin/` by a legitimate integration, or to overwrite the stored credential with an attacker-chosen value by sending an anonymous request carrying a crafted `Authorization: Basic` header. This is particularly impactful in environments using WordPress Application Passwords for REST API or third-party integrations, as those credentials are transmitted as HTTP Basic auth to `/wp-admin/` and will be silently harvested via this unauthenticated write path. CVE record
- CVE-2026-19949, 25 Aug 2026
- The All-in-One WP Migration and Backup plugin for WordPress is vulnerable to SQL Injection via archive restore functionality in all versions up to, and including, 7.109 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This can be leveraged to obtain the ai1wm_secret_key when a site administrator performs an archive restore and achieve remote code execution once able to leverage the ai1wm_secret_key value. CVE record
- CVE-2026-17533, 16 Aug 2026
- The All-in-One WP Migration and Backup WordPress plugin before 7.108 does not restrict its migration import functionality to network administrators on multisite installations, allowing an administrator of a single subsite to execute arbitrary PHP code across the entire network. CVE record
- CVE-2026-12898, 20 Jul 2026
- The All-in-One WP Migration and Backup WordPress plugin before 7.106 does not properly sanitise a user-supplied value before using it to build a file path, allowing unauthenticated attackers to create or append a log file in arbitrary locations outside its intended storage directory. CVE record
- CVE-2025-8490, 27 Aug 2025
- The All-in-One WP Migration and Backup plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Import in all versions up to, and including, 7.97 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled. CVE record
- CVE-2024-10942, 13 Mar 2025
- The All-in-One WP Migration and Backup plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 7.89 via deserialization of untrusted input in the 'replace_serialized_values' function. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code. An administrator must export and restore a backup in order to trigger the exploit. CVE record
- CVE-2024-9162, 28 Oct 2024
- The All-in-One WP Migration and Backup plugin for WordPress is vulnerable to arbitrary PHP Code Injection due to missing file type validation during the export in all versions up to, and including, 7.86. This makes it possible for authenticated attackers, with Administrator-level access and above, to create an export file with the .php extension on the affected site's server, adding an arbitrary PHP code to it, which may make remote code execution possible. CVE record
- CVE-2024-8852, 22 Oct 2024
- The All-in-One WP Migration and Backup plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 7.86 through publicly exposed log files. This makes it possible for unauthenticated attackers to view potentially sensitive information such as full paths contained in the exposed log files. CVE record
- CVE-2022-2546, 2 Feb 2023
- The All-in-One WP Migration WordPress plugin before 7.63 uses the wrong content type, and does not properly escape the response from the ai1wm_export AJAX action, allowing an attacker to craft a request that when submitted by any visitor will inject arbitrary html or javascript into the response that will be executed in the victims session. Note: This requires knowledge of a static secret key CVE record
- CVE-2022-1476, 10 May 2022
- The All-in-One WP Migration plugin for WordPress is vulnerable to arbitrary file deletion via directory traversal due to insufficient file validation via the ~/lib/model/class-ai1wm-backups.php file, in versions up to, and including, 7.58. This can be exploited by administrative users, and users who have access to the site's secret key. CVE record
What to do if you run All-in-One WP Migration and Backup
If you run All-in-One WP Migration and Backup, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new All-in-One WP Migration and Backup vulnerabilities
Free. We email you when a new vulnerability is published for All-in-One WP Migration and Backup, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.