CVE-2026-8442
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 Arbitrary File Deletion in versions up to and including 12.6.8. This is due to missing authorization checks on the wpfb_hide_review and wprp_save_review_admin AJAX handlers combined with insufficient path validation in the wpfb_hidereview_ajax() function, which uses strpos() to check that a stored media URL starts with the expected prefix but fails to sanitize path traversal sequences in the remaining relative path before passing it to unlink(). This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary files on the affected site's server which may make remote code execution possible.
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 versions up to 12.6.8 contains an arbitrary file deletion vulnerability due to missing authorization checks on AJAX handlers (wpfb_hide_review and wprp_save_review_admin) combined with insufficient path validation that uses strpos() to check a prefix but fails to sanitize path traversal sequences before passing the path to PHP's unlink() function, allowing authenticated subscribers to delete arbitrary files.
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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm 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/wp-review-slider-pro/ for a version fileAffected if Plugin is installed and active
-
Identify installed plugin versionCheck the plugin header in wp-review-slider-pro/wp-review-slider-pro.php for 'Version: X.X.X' or look for a version constant in the main plugin fileAffected if Version is 12.6.8 or lower
-
Verify low-privilege user roles existGo to WordPress admin > Users and check if any users have the 'Subscriber' role assignedAffected if At least one Subscriber-level user account exists on the site
-
Test AJAX endpoint accessibilitySend a POST request to /wp-admin/admin-ajax.php with action=wpfb_hide_review or action=wprp_save_review_admin, authenticated as a subscriber-level user, and observe if the request is processed without a capability errorAffected if The AJAX handlers respond to subscriber-level authentication without returning a capability/authorization error
User is affected if WP Review Slider Pro version 12.6.8 or lower is installed, the plugin is active, and subscriber-level users can access the wpfb_hide_review or wprp_save_review_admin AJAX endpoints.
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.
From vendor dataUpdate to version 12.6.9 or later which should include proper authorization checks and path traversal sanitization; alternatively, restrict AJAX endpoint access to users with higher privileges until the patch can be applied.
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8442 — 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-8442 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