Widgets for Google Reviews <= 13.3 - Authenticated (Editor+) Stored Cross-Site Scripting via 'fomo-title' and 'fomo-text' Parameters
The Widgets for Google Reviews plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 13.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with editor-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.
Quick answer
Widgets for Google Reviews should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- *-13.3
Fixed versions
- 13.3.1
How to fix it
Widgets for Google Reviews is affected by CVE-2026-11591, a cross-site scripting issue in versions up to 13.3. Wordfence lists the official remediation as updating to version 13.3.1, or a newer patched version. Prioritize internet-facing WordPress sites, sites with public registration, customer portals, support, booking, import/export, page-builder, and admin workflows where the vulnerable feature is enabled. If immediate patching is not possible, disable the affected plugin or feature, restrict access, and monitor for exploitation until the update is installed.
- Inventory every WordPress site that has Widgets for Google Reviews installed, including production, staging, multisite, client, WooCommerce, support, booking, and content-management environments.
- Confirm the installed Widgets for Google Reviews version and compare it with the affected range from the Wordfence advisory.
- Update Widgets for Google Reviews to version 13.3.1, or to a newer vendor-supported patched version from the official WordPress update channel.
- If the update cannot be applied immediately, disable Widgets for Google Reviews or the affected feature and restrict access with roles, authentication, WAF rules, or temporary route blocking.
- Review user-generated content, forms, widgets, saved plugin settings, comments, profiles, templates, support tickets, page-builder output, and WooCommerce/customer pages for injected scripts or unexpected HTML.
- Rotate administrator sessions, API keys, webhook secrets, payment or integration tokens, and affected credentials if logs or content review suggest compromise.
- Clear WordPress, object, CDN, page-builder, security plugin, WooCommerce, booking/support plugin, and browser caches after patching so vulnerable assets or stored payloads are not served.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the running Widgets for Google Reviews version is version 13.3.1 or newer, and record the patched version in the remediation ticket.
- Verify the affected fields, widgets, forms, profile data, ticket content, page-builder output, or settings now sanitize input and escape output instead of rendering executable scripts.
- Review web server, WordPress, security plugin, WAF, database, WooCommerce, booking/support, and application logs for exploitation attempts before and after the fix.
- Retest normal visitor, subscriber, customer, editor, administrator, checkout, form, API, booking, support ticket, import/export, backup/restore, snippet, or integration workflows to confirm expected behavior still works.
- Run a fresh Fixnx scan and document the public exposure state, patched version, log review, and any cleanup evidence.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-11591?
Widgets for Google Reviews versions listed as affected should be reviewed: *-13.3.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.