CVE-2026-17555
MediumCVSS 4.9Exploitation Probability (EPSS)
Low risk19th percentile - higher than 19% of all known CVEs
Summary
The WPvivid Backup & Migration plugin for WordPress up to version 0.9.131 contains a SQL Injection vulnerability via the export_data parameter. Authenticated attackers with administrator-level access and above can append additional SQL queries to existing queries, allowing extraction of sensitive database information.
Risk Assessment
Attackers can access the entire database, including user data, passwords, and other confidential information, potentially leading to full system compromise.
Recommendation
Immediately update the WPvivid Backup & Migration plugin to the latest version and restrict administrator privileges to trusted users only.
Other vulnerabilities in WPvivid Backup & Migration
See all- CVE-2025-12656Low
Vulnerability in the WPvivid Backup & Migration WordPress plugin (up to version 0.9.128) allows an authenticated attacker with Administrator-level access to delete arbitrary directories on the server via the delete_cancel_staging_site() function due to insufficient path validation.
- CVE-2025-12654Low
The Migration, Backup, Staging – WPvivid Backup & Migration plugin for WordPress is vulnerable to arbitrary directory creation in all versions up to, and including, 0.9.120. The check_filesystem_permissions() function does not properly restrict the directories that can be created or their location, allowing authenticated attackers with Administrator-level access to create arbitrary directories.
Original NVD description (English source)
The WPvivid Backup & Migration plugin for WordPress is vulnerable to SQL Injection via the export_data parameter in versions up to, and including, 0.9.131. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. The values are received in prepare_export_post(), passed through sanitize_text_field() and stripslashes(), JSON-decoded, and the attacker-controlled JSON object keys are collected as $posts_ids without integer casting. They are stored in the export task options and later joined with commas and interpolated directly into a `WHERE ID IN (...)` clause inside a $wpdb->get_results() call in export_post_to_xml() (unquoted, numeric context), with no $wpdb->prepare() or esc_sql(). This makes it possible for authenticated attackers, with Administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS

