Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessPost crafted malicious Google review
-
DeliveryDefault daily cron auto-imports review
-
ExploitPayload stored without sanitization
-
ExecutionScript executes on visitor DOMContentLoaded
-
ImpactSteal sessions or redirect visitors
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 a WordPress site running Rich Showcase for Google Reviews (widgetpack) ≤7.1.3 that is connected to a Google business profile and rendering imported reviews. Two delivery paths exist: (1) an authenticated user with subscriber-level access or above injecting via the 'reviews[].text' parameter (vendor PR:L), and (2) an unauthenticated attacker posting a crafted Google review on the connected business, which the plugin's default daily auto-import cron ingests with no WordPress credentials. Limiting factors: the malicious review only takes effect after the daily cron import (a delay, not a race), execution only occurs on pages that display the imported reviews, and the site must have the auto-import feature enabled (default) and the plugin connected to a business. Once stored, no user interaction is needed - it triggers for every visitor on DOMContentLoaded. |
| Impact | The vendor (Wordfence) CVSS 3.1 score is 6.4 (medium) using CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N, reflecting an authenticated subscriber-level stored XSS. However, this score understates a key signal in the description: the payload can also be delivered with NO WordPress account by posting a crafted Google review for the connected business, which the plugin's default daily cron then auto-imports - this is effectively an unauthenticated injection path, conflicting with the vendor's PR:L and arguing for PR:N in real-world terms. Offsetting factors keep this from being a top-tier emergency: impact is limited (C:L/I:L, no availability or full compromise), it is a client-side script-execution flaw rather than server RCE, and the product is a niche plugin. No EPSS score, no CISA KEV listing, and no public POC are present in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation - do not treat it as weaponized. Net: a moderate-priority patch, elevated above a routine subscriber-XSS because the auto-import vector requires no account and the payload executes for every visitor with no user interaction, but bounded by limited technical impact and modest deployment footprint. EPSS and SSVC data are missing and should be checked to finalize prioritization. |
| Exploit ScenarioDerived | An attacker posts a Google review containing a JavaScript payload on the business profile connected to the plugin; the plugin's default daily cron auto-imports the review text without sanitization. When any visitor loads a page displaying the imported reviews, the script executes on DOMContentLoaded with no further interaction, enabling session/cookie theft, redirects, or drive-by actions in the victim's browser. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 03, 2026
Stored cross-site scripting in the Rich Showcase for Google Reviews WordPress plugin (widgetpack) affects all versions up to and including 7.1.3 and lets injected JavaScript run for every visitor of any page that renders imported Google reviews. Two delivery paths are confirmed by the available data: a WordPress user with subscriber-level access or above can inject script through the 'reviews[].text' parameter, and - because the plugin's default daily cron auto-imports review content from the connected Google business profile - an unauthenticated attacker can plant the payload by posting a crafted Google review on that business, with no WordPress credentials required; our independent assessment scores this path CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N (the vendor's 6.4 uses PR:L for the authenticated path). Once stored, the payload executes on DOMContentLoaded without further user interaction, though exploitation is gated by the daily import cycle, an enabled auto-import feature, an active Google Business connection, and display of the affected review block; no public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV).
RemediationAI
The supplied data points to an upstream fix in the WordPress.org plugin repository at changeset 3719682 (https://plugins.trac.wordpress.org/changeset?reponame=&old=3719682%40widget-google-reviews&new=3719682%40widget-google-reviews), i.e. upstream fix available (PR/commit); a released patched version number is not independently confirmed from the provided input, so administrators should update the plugin to the latest available release above 7.1.3 and verify the changelog rather than assuming a specific version. Until the update is applied, the most effective compensating control is to disable the plugin's automatic Google review import cron and disconnect or pause the Google Business Profile integration - this severs the unauthenticated delivery path (attacker-posted reviews are never ingested) at the cost of losing automatic review refresh, and it also blocks the authenticated subscriber path from receiving new attacker-controlled content. Additional layered mitigations, each with trade-offs: remove the plugin's review widget from all public pages or unpublish the affected review block (eliminates the execution sink but removes the business value of the feature); restrict or audit low-privilege WordPress accounts (subscriber and above) since the vendor's PR:L path relies on them, noting this does nothing against the unauthenticated Google-review path; and apply a Content Security Policy that disallows inline and third-party script execution for the site, which can neutralize the injected payload but risks breaking legitimate theme and plugin JavaScript and requires careful tuning. After patching, review the WordPress database for stored review content containing script markup or unexpected HTML and re-import or purge the affected review records, since the stored XSS survives until the poisoned entries are removed.
Affected VersionsENISA
Affected Packages
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 affected component is the WordPress plugin 'Rich Showcase for Google Reviews' (CPE cpe:2.3:a:widgetpack:rich_showcase_for_google_reviews:*:*:*:*:*:*:*:*; slug widget-google-reviews), a widget that fetches, stores, and renders reviews from a connected Google Business Profile. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation / Cross-Site Scripting): review text pulled from the Google API is persisted without adequate sanitization and later emitted without context-appropriate output escaping. The referenced source lines trace the full data flow - includes/core/class-google-dao.php lines 410 and 445 handle the ingestion/persistence of the review objects, includes/class-view.php lines 453 and 535 handle rendering the stored review data into the page, and assets/7.1.2/js/public-main.js line 14 shows the front-end script that acts on the DOM at DOMContentLoaded, which is why the stored markup is interpreted automatically for every visitor rather than requiring a click. The S:C scope change in the CVSS vectors reflects that the injected script executes in the context of the host WordPress site and can reach resources beyond the vulnerable component itself, while C:L/I:L/A:N reflects limited confidentiality and integrity impact on the site and its users (for example, session or cookie theft, content tampering, redirects, or malicious script delivery) with no direct availability impact.
Know when Rich Showcase For Google Reviews 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
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Primary delivery via an auto-imported Google review needs no WordPress account (PR:N, above vendor's PR:L); network stored XSS with scope change (S:C) and limited C/I, no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Rich Showcase for Google Reviews plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'reviews[].text' parameter in all versions up to, and including, 7.1.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload is delivered entirely through a Google review posted for the connected business and requires no WordPress account; the plugin's default daily cron auto-imports the malicious review text, and execution triggers for every visitor on DOMContentLoaded without any further user interaction.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Stored cross-site scripting in the Rich Showcase for Google Reviews WordPress plugin allows authenticated attackers with
A Stored Cross-Site Scripting (XSS) vulnerability exists in the Rich Showcase for Google Reviews widget (richplugins plu
EUVD-2026-91913
GHSA-xp9f-p9m6-662q
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB