Skip to main content

WP Yelp Review Slider CVE-2026-93778

| EUVDEUVD-2026-84306 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-09-22 Wordfence GHSA-45jh-6cpx-5764
7.2
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Post malicious Yelp review anonymously
  2. Delivery
    Admin imports reviews via Download Reviews
  3. Exploit
    Payload stored unsanitized in database
  4. Execution
    Unescaped output in slider template
  5. Impact
    Script executes in every page visitor's browser

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires the WP Yelp Review Slider plugin (versions up to and including 9.2) installed and the site administrator actively using the plugin's Download Reviews / import feature (wpyelp_download_source) to pull reviews from Yelp. The attacker must be able to publish a review containing the payload on the target business's public Yelp listing (no WordPress account needed). Limiting factors: the payload only reaches the database if and when the admin performs an import, and it only executes against users who subsequently visit a page rendering the affected slider template - so a site that never imports reviews, or has already sanitized/updated, is not exposed. The vendor's UI:N does not capture this required admin import action.

Impact

This is a genuine but conditional web-application risk, not an internet-scale emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N, base 7.2 HIGH) reflects a stored XSS where the effective attacker needs no WordPress account because the malicious payload is authored anonymously on Yelp and later ingested by the site itself. No EPSS score, no CISA KEV listing, and no public exploit code (POC) were provided, so exploitation is best characterized as 'no public exploit identified at time of analysis.' The absence of EPSS/KEV is consistent with a niche WordPress review-widget plugin rather than a mass-exploited target. One signal to scrutinize: the vendor sets UI:N, yet the injection path actually depends on a site administrator running the plugin's Download Reviews import - a required human action by a second party. Under strict CVSS scoring that admin step is arguably UI:R (which would lower the base to roughly 6.1), so the 7.2 should be read as a slight over-statement of how push-button the attack is. Net: a real priority for sites running this plugin and importing reviews, but the multi-step, operator-dependent chain keeps real-world risk moderate rather than critical.

Exploit ScenarioDerived

An attacker posts a Yelp review on a target business's public Yelp page containing a script payload (e.g., an <img onerror=...> or <script> tag) instead of ordinary review text. When the WordPress site administrator later uses the plugin's Download Reviews feature (wpyelp_download_source) to sync Yelp reviews, the unsanitized payload is stored in the database and rendered unescaped in the front-end slider template, executing in the browser of every visitor who views the page. No public exploit code is identified, but the technique is trivial and requires no WordPress credentials.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 22, 2026

Stored cross-site scripting in the WP Yelp Review Slider WordPress plugin (all versions up to and including 9.2) lets an unauthenticated attacker plant arbitrary JavaScript that executes in the browser of anyone viewing a page that renders the affected review slider. The payload enters through the Yelp review text pulled in by the plugin's Download Reviews import routine (wpyelp_download_source), so an anonymous party simply publishes a booby-trapped review on the target business's public Yelp listing and waits for a site administrator to import it; no WordPress account on the victim site is needed. This is a conditional, not internet-scale, risk: exploitation requires the admin to actually run an import, and code only fires for subsequent visitors to the affected page, so sites that never import reviews or that have updated past the vulnerable builds are not exposed. No public exploit code was identified at time of analysis and the issue is not in CISA KEV.

RemediationAI

Upstream fix available (plugin repository changeset); released patched version not independently confirmed - operators should check the WordPress plugin directory for a WP Yelp Review Slider release later than 9.2 that incorporates changeset 3704718 (https://plugins.trac.wordpress.org/changeset?reponame=&old=3704718%40wp-yelp-review-slider&new=3704718%40wp-yelp-review-slider) and update to that build as soon as it is published, verifying the deployed version number rather than assuming the fix is live. Where updating is not yet possible, the most effective compensating control is to stop using the Download Reviews / wpyelp_download_source import function altogether, since the payload can only reach the database through that admin-triggered action - the trade-off is that the slider will display only previously imported or manually entered reviews; additionally, review rows already stored should be purged or manually sanitized before the slider is rendered again, otherwise previously imported payloads will keep executing. Site owners can further reduce exposure by removing the plugin if it is not essential, by restricting who can access the plugin's admin pages, and by applying a web application firewall rule or Content-Security-Policy that blocks inline/reflected script execution in slider output, though CSP tuning carries a risk of breaking other front-end functionality and must be tested before enforcement. The Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/df6cbc36-d136-49c1-81f0-a61cb91f0ad7?source=cve should be monitored for a confirmed patched version and any updated guidance.

Affected VersionsENISA

WP Yelp Review Slider 0 ≤9.2

Affected Packages

euvd wp_yelp_review_slider no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a classic CWE-79 improper neutralization of input during web page generation (stored/persistent XSS) in a third-party WordPress plugin identified by CPE cpe:2.3:a:jgwhite33:wp_yelp_review_slider:*:*:*:*:*:*:*:*. Yelp review content retrieved by the admin-side import function wpyelp_download_source (see class-wp-yelp-review-slider-admin.php around lines 1140, 1336, 1358 and 1659) is written into the WordPress database without adequate sanitization, and it is later echoed unescaped by the front-end rendering templates (public/partials/template_style_1.php around lines 95 and 129). Because the tainted data crosses a trust boundary from a public third-party platform into the site's own database and back out into HTML, the script executes in the origin of the victim WordPress site rather than Yelp's, giving the injected payload the site's cookies, session context and DOM access. The CVSS scope change (S:C) reflects that a plugin-scoped input flaw ends up compromising users of the broader WordPress site; the low confidentiality and integrity ratings reflect script execution limited to the client browser rather than server-side compromise. Our independent assessment adjusts the vendor vector from UI:N to UI:R, since the vendor's scoring does not capture the required administrator action of triggering the Download Reviews import.

Know when Wp Yelp Review Slider gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY 7.2 HIGH
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
vuln.today AI 6.1 MEDIUM

Unauthenticated remote injection (PR:N) via public Yelp, but exploitation depends on the admin running the import, so UI:R; stored XSS crosses into the visitor's browser (S:C) with limited C/I impact.

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

The WP Yelp Review Slider plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Yelp Review Text (imported via wpyelp_download_source) in all versions up to, and including, 9.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The malicious payload originates from an anonymous Yelp reviewer on a public platform and requires no WordPress account; it is introduced into the database during the site administrator's ordinary use of the plugin's Download Reviews feature, making the effective attacker unauthenticated.

Executive ViewAI

Why It Matters

The WP Yelp Review Slider plugin (all versions up to and including 9.2) contains a stored cross-site scripting vulnerability that could let attackers inject malicious JavaScript into web pages via imported Yelp reviews. This could result in theft of visitor session data, website defacement, or further compromise, affecting customers and damaging brand trust. Because no vendor-released patch is identified at time of analysis and the attack requires an administrator to import a booby-trapped review, immediate risk mitigation is critical for any site using this plugin.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include disabling the plugin, disabling the review import feature (wpyelp_download_source), manually vetting Yelp reviews before import, enforcing a Content Security Policy (CSP) to block inline scripts, and deploying WAF rules to filter XSS payloads.

Threat Intelligence Overview

EPSS Score
0.2%
Top 84% exploitable
Prevalence
Low
Niche WordPress review-slider plugin with limited install base
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy