Unauthenticated stored XSS via unsanitized content webhook
Published Oct 11, 2026 · Updated Oct 11, 2026
Stored XSS in Topcontent WordPress Plugin 1.2.1 and earlier allows remote attackers to publish malicious posts via the content webhook. Its request handler improperly authorizes submissions and disables HTML sanitization before storing their content. Exploitation requires an API key that has never been configured; injected JavaScript executes when visitors view the malicious posts.
Summary
What happened
Stored XSS in Topcontent WordPress Plugin 1.2.1 and earlier allows remote attackers to publish malicious posts via the content webhook. Its request handler improperly authorizes submissions and disables HTML sanitization before storing their content. Exploitation requires an API key that has never been configured; injected JavaScript executes when visitors view the malicious posts.
The record
- CVE
- CVE-2026-88903
- Published
- Oct 11, 2026
- Updated
- Oct 11, 2026
- Vendor
- Topcontent
- Product
- Topcontent WordPress Plugin
- Classifications
- CWE-79, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 11, 2026CVE publishedPublication date reported by the CVE source.
- Oct 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.2.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started