dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-8443

HIGH · 8.8 CVSS v3.1 Published 2026-06-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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->get_results() without $wpdb->prepare(). 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in WP Review Slider Pro plugin allows authenticated users (Subscriber+) to inject arbitrary SQL via the 'stypes' and 'slocations' JSON parameters in the wppro_get_overall_chart_data AJAX action. The code uses stripslashes() before json_decode(), undoing WordPress's escaping, then concatenates decoded values directly into SQL WHERE clauses without $wpdb->prepare(), and even returns the executed SQL in the response to simplify exploitation.

MitigationReplace direct string concatenation with $wpdb->prepare() for all SQL queries using user input, add proper capability checks to the AJAX handler, and remove SQL debugging output from responses. Consider disabling the plugin or blocking the AJAX endpoint until a patch is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if WP Review Slider Pro is installed
    Check your WordPress plugins directory or WordPress admin panel for WP Review Slider Pro and note the installed version number
    Affected if The plugin is installed and you are using any version of WP Review Slider Pro (no specific version range was provided for this CVE)
  2. Verify AJAX action wppro_get_overall_chart_data exists
    Search plugin PHP files for the string 'wppro_get_overall_chart_data' or inspect the AJAX handler registration to confirm this action is registered
    Affected if The AJAX action wppro_get_overall_chart_data is present in the plugin code
  3. Confirm Subscriber role can access the AJAX endpoint
    Inspect the AJAX handler registration for wppro_get_overall_chart_data and check the capability check (or lack thereof) - look for 'add_action("wp_ajax_wppro_get_overall_chart_data"' without a capability check or with a low-privilege check like 'read'
    Affected if The AJAX handler is accessible to authenticated users with Subscriber role or lower privilege
  4. Locate vulnerable SQL construction code
    Search plugin files for the pattern where stripslashes() is called before json_decode() on user input from the AJAX request, followed by direct concatenation into SQL queries (look for code using the decoded 'stypes' or 'slocations' variables in WHERE clauses without $wpdb->prepare())
    Affected if Code contains stripslashes(json_decode(...)) on AJAX parameters and concatenates the decoded values directly into SQL queries without using $wpdb->prepare()

Your environment is affected if WP Review Slider Pro is installed, the wppro_get_overall_chart_data AJAX action is accessible to Subscriber-level users, and the plugin code contains the stripslashes/json_decode pattern with direct SQL concatenation for the stypes or slocations parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace direct string concatenation with $wpdb->prepare() for all SQL queries using user input, add proper capability checks to the AJAX handler, and remove SQL debugging output from responses. Consider disabling the plugin or blocking the AJAX endpoint until a patch is available.

Recommended fix High confidence

Version 12.6.9 or later

  1. 1. Log in to the WordPress admin dashboard with administrator privileges.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate 'WP Review Slider Pro' in the plugin list.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Alternatively, download the latest version from the official WordPress repository or the vendor's website.
  6. 6. Deactivate and re-activate the plugin if the update does not complete automatically.
  7. 7. Verify the plugin is now running version 12.6.9 or later.
  8. 8. Test the wppro_get_overall_chart_data AJAX functionality to confirm it still works correctly.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8443 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8443 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data