CVE-2026-8441
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 · uneditedThe WP Review Slider Pro plugin for WordPress is vulnerable to SQL Injection via the 'notinstring' parameter of the wprp_load_more_revs AJAX action in versions up to, and including, 12.7.2. The parameter is read via $_POST['notinstring'] and passed through sanitize_text_field() — which strips HTML and whitespace but does not provide SQL safety. The value is then concatenated directly into a numeric/unquoted `AND id NOT IN (...)` clause and executed via $wpdb->get_results() without $wpdb->prepare() or intval() casting. Because the value sits in an unquoted numeric context, WordPress's wp_magic_quotes protection (which only escapes embedded quotes) is ineffective. The AJAX hook is registered via wp_ajax_nopriv_wprp_load_more_revs, and the required check_ajax_referer nonce is publicly available via wp_localize_script on any frontend page that renders the plugin shortcode, so an unauthenticated attacker who can reach a public page hosting the plugin can extract arbitrary data from the database via blind/time-based injection.
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 confidenceThe WP Review Slider Pro plugin for WordPress has a SQL Injection vulnerability in the wprp_load_more_revs AJAX action. The 'notinstring' POST parameter is sanitized only with sanitize_text_field() and then directly concatenated into an unquoted numeric context in an AND id NOT IN (...) clause, executed via $wpdb->get_results() without $wpdb->prepare() or intval() casting. An unauthenticated attacker can exploit this via blind/time-based SQL injection to extract arbitrary database data.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP Review Slider Pro is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP Review Slider Pro', or check the plugin files in /wp-content/plugins/ for the plugin folder and read the main PHP file to find the version numberAffected if The plugin is installed and the version falls within the affected range (compare your installed version to the known vulnerable versions)
-
Confirm the vulnerable AJAX action existsCheck the plugin source code for the 'wprp_load_more_revs' AJAX action handler - look for add_action('wp_ajax_wprp_load_more_revs', ...) or add_action('wp_ajax_nopriv_wprp_load_more_revs', ...)Affected if The AJAX action handler is registered, especially if wp_ajax_nopriv_ is used (allowing unauthenticated access)
-
Check if AJAX is accessible to unauthenticated usersInspect the plugin code to see if the action is hooked to wp_ajax_nopriv_ (which allows unauthenticated attackers to send requests)Affected if The action is hooked to wp_ajax_nopriv_wprp_load_more_revs, meaning unauthenticated users can trigger the vulnerable endpoint
-
Identify the vulnerable parameter handlingSearch the plugin code for handling of the 'notinstring' POST parameter - look for $_POST['notinstring'] with sanitize_text_field() but without intval() casting or $wpdb->prepare() with %d placeholderAffected if The 'notinstring' parameter is sanitized only with sanitize_text_field() and used directly in the SQL query without integer casting or prepared statements
-
Test the endpoint for SQL injection susceptibilitySend a crafted POST request to /wp-admin/admin-ajax.php with action=wprp_load_more_revs and a test 'notinstring' value containing SQL syntax (e.g.,notinstring=1 AND SLEEP(5)) - observe if the response delaysAffected if The endpoint accepts the parameter and exhibits time-based behavior indicating SQL injection is possible
You are affected if the WP Review Slider Pro plugin is installed with a vulnerable version and the wprp_load_more_revs AJAX action is exposed to unauthenticated users without proper integer casting on the notinstring parameter.
Generated from the published advisory. Verify against your own configuration.
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 · scopedReplace the direct concatenation with $wpdb->prepare() using proper type placeholders (e.g., %d for integers) or cast the input to intval() before using it in the query. Until a patch is available, consider disabling the plugin or restricting AJAX access.
Latest version after 12.7.2 (vendor should provide 12.7.3 or higher with security fix)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate WP Review Slider Pro in the plugin list
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. If no update appears in WordPress, manually download the latest version from the official WordPress plugin repository or the vendor's website
- 6. Deactivate the current plugin version, then upload and install the new version
- 7. Clear any caching plugins or server-side caches after updating
- 8. Verify the plugin functions correctly on the frontend by loading a page with the review slider shortcode
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8441 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8441 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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