{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-8443 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-8443 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-8443 is a high-severity SQL injection vulnerability in https://wpreviewslider.com/ WP Review Slider Pro, published on 16 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-8443 and fix it if it is affected.\n\nWhat it is: CVE-2026-8443 is a high-severity SQL injection vulnerability in https://wpreviewslider.com/ WP Review Slider Pro, published on 16 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-8443 in the wild and no public exploit code.\n\nAffected product: https://wpreviewslider.com/ WP Review Slider Pro. 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-8443/ (Markdown: https://insights.sbomify.com/CVE-2026-8443/index.md)","id":"CVE-2026-8443","markdown":"https://insights.sbomify.com/CVE-2026-8443/index.md","name":"CVE-2026-8443","record":{"aliases":["GHSA-m8xj-3v37-wrp9"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated attackers can exploit SQL injection in WP Review Slider Pro to extract sensitive database information via vulnerable AJAX parameters.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"The WP Review Slider Pro plugin for WordPress is vulnerable to SQL Injection via the 'stypes' and 'slocations' parameters of the wppro_get_overall_chart_data AJAX action in versions up to, and including, 12.6.8. This is due to the use of stripslashes() on user-supplied JSON strings prior to json_decode(), which removes the escaping applied by WordPress's wp_magic_quotes; the resulting decoded array values are then concatenated directly into SQL WHERE clauses without parameterization, and the constructed query is executed via $wpdb-\u003eget_results() without $wpdb-\u003eprepare(). This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The handler also returns the executed SQL string in its JSON response, which simplifies oracle construction for blind exploitation.","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":"WP Review Slider Pro \u003c= 12.6.8 - Authenticated (Subscriber+) SQL Injection via 'stypes' Parameter","id":"CVE-2026-8443","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"WP Review Slider Pro \u003c= 12.6.8 - Authenticated (Subscriber+) SQL Injection via 'curselrevs' Parameter","id":"CVE-2026-8444"},"packages":[],"prev":{"headline":"WP Review Slider Pro \u003c= 12.6.8 - Authenticated (Subscriber+) Arbitrary File Deletion via 'myaction' Parameter","id":"CVE-2026-8442"},"products":["WP Review Slider Pro"],"published":"2026-06-16","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":"total"},"state":"PUBLISHED","updated":"2026-06-16","vendors":["https://wpreviewslider.com/"]},"summary":"Authenticated attackers can exploit SQL injection in WP Review Slider Pro to extract sensitive database information via vulnerable AJAX parameters.","url":"https://insights.sbomify.com/CVE-2026-8443/"}