{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-17555 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-17555 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-17555 is a medium-severity SQL injection vulnerability in wpvividplugins WPvivid — Backup, Migration \u0026 Staging, published on 1 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-17555 and fix it if it is affected.\n\nWhat it is: CVE-2026-17555 is a medium-severity SQL injection vulnerability in wpvividplugins WPvivid — Backup, Migration \u0026 Staging, published on 1 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-17555 in the wild and no public exploit code.\n\nAffected product: wpvividplugins WPvivid — Backup, Migration \u0026 Staging. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-17555/ (Markdown: https://insights.sbomify.com/CVE-2026-17555/index.md)","id":"CVE-2026-17555","markdown":"https://insights.sbomify.com/CVE-2026-17555/index.md","name":"CVE-2026-17555","record":{"aliases":["GHSA-5c57-362f-vw84"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Authenticated administrators can exploit SQL injection in the WPvivid plugin to extract sensitive database information.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"The WPvivid Backup \u0026 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-\u003eget_results() call in export_post_to_xml() (unquoted, numeric context), with no $wpdb-\u003eprepare() 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"WPvivid \u003c= 0.9.131 - Authenticated (Administrator+) SQL Injection via 'export_data' Parameter","id":"CVE-2026-17555","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Path traversal in Enterprise Server","id":"CVE-2026-17556"},"packages":[],"prev":{"headline":"Privilege escalation in Shopping Cart \u0026 eCommerce Store","id":"CVE-2026-17553"},"products":["WPvivid — Backup, Migration \u0026 Staging"],"published":"2026-08-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-03","vendors":["wpvividplugins"]},"summary":"Authenticated administrators can exploit SQL injection in the WPvivid plugin to extract sensitive database information.","url":"https://insights.sbomify.com/CVE-2026-17555/"}