CVE-2026-88903

Topcontent <= 1.2.1 - Unauthenticated Stored XSS via Content Webhook

  • High 8.8
  • A public exploit reference is listed

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.

Key facts

Published
11 Oct 2026
Last changed
11 Oct 2026
Assigned by
WPScan
EPSS
0.276% likely to be exploited in the next 30 days, higher than 20.27% of CVEs (scores for 18 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 8.8CVSS 3.1, Highfrom CISA (ADP container)CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
UnknownTopcontent
  • Default status: unknown
  • 0 up to and including 1.2.1 (affected)

Timeline

  1. 11 Oct 2026 Published

Weakness

Practice this bug class

HackZoneLabs has a hands-on lab on XSS (stored, reflected, DOM) (CWE-79).

References