CVE-2026-88903 Topcontent <= 1.2.1 - Unauthenticated Stored XSS via Content Webhook
Unauthenticated attackers can inject malicious JavaScript into posts via webhook if the plugin's API key is unconfigured, leading to stored XSS.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-88903?
CVE-2026-88903 is a high-severity cross-site scripting vulnerability in Unknown Topcontent, published on 11 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-79
Which versions are affected by CVE-2026-88903?
How do I fix CVE-2026-88903?
No fix has been published for CVE-2026-88903 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-88903 being exploited?
There is no known exploitation of CVE-2026-88903 in the wild and no public exploit code.
Sources
Also known as GHSA-vrpv-vc9c-j35f.