Skip to main content
Menu
CVEs

Gemini Labs Site Reviews stored cross-site scripting in review pages

Affects the WordPress Site Reviews plugin version 8.3.7 and earlier, with the fix in version 8.3.8. No vendor severity rating is given, only the CVSS score of 7.1.

CVE-2026-129017Published , updated

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 8.3.8
Who is exposed
Specific setups only

Summary

Gemini Labs' Site Reviews plugin for WordPress contains a stored cross-site scripting flaw that lets an attacker plant malicious script in pages that other users then load. The attack can be launched remotely without logging in, but it requires a user to take an action, such as opening a crafted page.

Written by a model

Original description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Gemini Labs Site Reviews site-reviews allows Stored XSS.This issue affects Site Reviews: from n/a through 8.3.7.

Who should check

Sites running the WordPress Site Reviews plugin (Gemini Labs) version 8.3.7 or earlier.

“WordPress Site Reviews Plugin <= 8.3.7 is vulnerable”

patchstack.com

What to do

  1. Check whether your setup matches what the bug needs.

    WordPress Site Reviews plugin version 8.3.7 or earlier
  2. Upgrade to a fixed version: 8.3.8.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129017 (WordPress Site Reviews plugin <= 8.3.7 - Cross Site Scripting (XSS) vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129017 (entry last updated 2026-11-20):
Affected:
- Gemini Labs Site Reviews: fixed in 8.3.8
Fixed versions: 8.3.8.
Conditions (all must be true for the bug to be hit):
- WordPress Site Reviews plugin version 8.3.7 or earlier (source: https://patchstack.com/database/wordpress/plugin/site-reviews/vulnerability/wordpress-site-reviews-plugin-8-3-7-cross-site-scripting-xss-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-129017 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129017 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/site-reviews/vulnerability/wordpress-site-reviews-plugin-8-3-7-cross-site-scripting-xss-vulnerability?_s_id=cve
- https://www.cve.org/CVERecord?id=CVE-2026-129017
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129017
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129017"}.

Affected versions

cve.now Index

19Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 3

Questions about CVE-2026-129017

Is CVE-2026-129017 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

This is a stored cross-site scripting flaw, meaning malicious scripts can be injected into the site. The advisory says these scripts can steal visitor data or hijack accounts.

Source: patchstack.com, cve.org

Which versions are affected by CVE-2026-129017?

site-reviews: through 8.3.7 (fixed in 8.3.8).

Source: cve.now feed data

Am I affected, and how do I check?

The WordPress Site Reviews plugin, version 8.3.7 and earlier, is listed as vulnerable. The installed version can be checked on the Plugins screen in the WordPress admin area.

Source: patchstack.com, cve.org

How do I fix CVE-2026-129017?

Update the Site Reviews plugin to version 8.3.8 or later, the fixed version named in the advisory. The advisory asks for the latest available version, which is at least 8.3.8.

Source: patchstack.com, cve.org

No corrections so far. Something wrong on this page? Report an error.