CVE-2026-32491
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in jgwhite33 WP Review Slider wp-facebook-reviews allows Stored XSS.This issue affects WP Review Slider: from n/a through <= 13.9.
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 · moderate confidenceThis is a Stored Cross-Site Scripting (XSS) vulnerability in the WP Review Slider WordPress plugin (wp-facebook-reviews component) by jgwhite33. The vulnerability allows an attacker to inject malicious JavaScript code through review data that gets stored in the database and executed when other users view the reviews on the affected website.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
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 plugin is installedAccess WordPress admin panel, navigate to Plugins > Installed Plugins, and search for 'WP Review Slider' or 'wp-facebook-reviews'. Alternatively, check the /wp-content/plugins/ directory for the wp-facebook-reviews folder.Affected if The plugin folder 'wp-facebook-reviews' exists in the WordPress plugins directory
-
Identify the installed plugin versionIn WordPress admin, click on the WP Review Slider plugin to view details and version number. Alternatively, check the main plugin file header in /wp-content/plugins/wp-facebook-reviews/ for the Version field.Affected if Version cannot be determined or version falls within an unpatched release range
-
Confirm wp-facebook-reviews component is activeCheck WordPress admin > Plugins > Active Plugins list for 'WP Review Slider' or any active shortcode or widget using wp-facebook-reviews functionality. Look for shortcodes like [wprevp] or [fb_reviews] in page/post content.Affected if The plugin is active and its shortcodes or widgets are being used on the site
-
Inspect review display output for XSS vulnerabilityView a page or post containing Facebook reviews (look for shortcodes like [fb_reviews] or [wprevp]). View the page source and examine the HTML output for review text fields (name, review content, rating text) to see if data is properly escaped or rendered as raw HTML.Affected if Review data appears to render as raw HTML without sanitization (visible <script> tags, unescaped quotes in attributes, or review text containing HTML elements that execute)
The site is affected if the WP Review Slider plugin with the wp-facebook-reviews component is installed, active, and displaying Facebook reviews without proper output encoding of stored review data.
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 dataUpgrade to a patched version of WP Review Slider that properly sanitizes/escapes review data before displaying it. Until a patch is available, implement additional output encoding on the frontend and consider Content-Security-Policy headers to mitigate XSS risks.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32491 — 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-32491 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