Cross-site scripting in review widget business name

Check whether my systems are affected by CVE-2026-125711 (Trustindex Review Widget Plugins < 14.3 - Editor+ Stored XSS via Business Name), 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-125711 (entry last updated 2026-11-13):
Affected:
- Unknown Widgets for Google Reviews: fixed in 14.3
- Unknown WP Tripadvisor Review Widgets: fixed in 14.3
- Unknown Widgets for Booking.com Reviews: fixed in 14.3
- Unknown Widgets for Reviews & Recommendations: fixed in 14.3
- Unknown Widgets for Airbnb Reviews: fixed in 14.3
- Unknown Widgets for Yelp Reviews: fixed in 14.3
- Unknown Widgets for Amazon Reviews: fixed in 14.3
- Unknown Widgets for Thumbtack Reviews: fixed in 14.3
- Unknown Widgets for Ebay Reviews: fixed in 14.3
- Unknown Widgets for Zillow Reviews: fixed in 14.3
- and 11 more affected products, listed on https://cve.now/CVE-2026-125711
Fixed versions: 14.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-125711 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125711 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:
- the references on https://cve.now/CVE-2026-125711
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-125711
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-125711"}.