CVE-2026-17555: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in wpvividplugins WPvivid — Backup, Migration & Staging
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.
AI Analysis
Technical Summary
The WPvivid Backup & Migration plugin for WordPress (versions <=0.9.131) is vulnerable to SQL Injection through the export_data parameter. The vulnerability stems from insufficient escaping and lack of parameterized queries in the export_post_to_xml() function, where attacker-controlled JSON object keys are collected and directly interpolated into a SQL WHERE clause without integer casting or use of $wpdb->prepare() or esc_sql(). This allows authenticated administrators to append additional SQL commands to extract sensitive data from the database. The vulnerability is tracked as CVE-2026-17555 with a CVSS 3.1 base score of 4.9 (medium severity). No known exploits in the wild or vendor patches have been reported as of the publication date.
Potential Impact
An authenticated user with Administrator-level access or higher can exploit this vulnerability to perform SQL Injection attacks. This can lead to unauthorized disclosure of sensitive information from the WordPress database. The vulnerability does not affect confidentiality, integrity, or availability beyond data disclosure. There are no reports of active exploitation in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict Administrator-level access to trusted users only and monitor for suspicious activity related to export tasks. Avoid using the vulnerable export_data functionality if possible.
CVE-2026-17555: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in wpvividplugins WPvivid — Backup, Migration & Staging
Description
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.
CVSS v3.1
Score 4.9medium
Affected software
wpvividplugins
WPvivid — Backup, Migration & Staging
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The WPvivid Backup & Migration plugin for WordPress (versions <=0.9.131) is vulnerable to SQL Injection through the export_data parameter. The vulnerability stems from insufficient escaping and lack of parameterized queries in the export_post_to_xml() function, where attacker-controlled JSON object keys are collected and directly interpolated into a SQL WHERE clause without integer casting or use of $wpdb->prepare() or esc_sql(). This allows authenticated administrators to append additional SQL commands to extract sensitive data from the database. The vulnerability is tracked as CVE-2026-17555 with a CVSS 3.1 base score of 4.9 (medium severity). No known exploits in the wild or vendor patches have been reported as of the publication date.
Potential Impact
An authenticated user with Administrator-level access or higher can exploit this vulnerability to perform SQL Injection attacks. This can lead to unauthorized disclosure of sensitive information from the WordPress database. The vulnerability does not affect confidentiality, integrity, or availability beyond data disclosure. There are no reports of active exploitation in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict Administrator-level access to trusted users only and monitor for suspicious activity related to export tasks. Avoid using the vulnerable export_data functionality if possible.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-07-27T12:52:12.175Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a6dba19bf32cb7a347ed915
Added to database: 08/01/2026, 09:19:21 UTC
Last enriched: 08/08/2026, 14:25:57 UTC
Last updated: 09/14/2026, 12:44:41 UTC
Views: 72
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.