Topcontent Plugin Unauthenticated Post Publication with XSS

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.

Casky was already ahead

This CVE exploits attack patterns that Casky's 323matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

The Topcontent WordPress plugin through version 1.2.1 contains a critical authorization bypass combined with improper input sanitization. An unauthenticated attacker can exploit a request handler that lacks proper permission checks to publish arbitrary posts containing malicious JavaScript directly to any WordPress site using the plugin—provided the API key has never been configured. This vulnerability is particularly dangerous because it requires no authentication and affects the core content publishing mechanism, allowing attackers to inject persistent XSS payloads that execute in the browsers of all site visitors. WordPress administrators and users of this plugin face immediate risk of site compromise, data theft, and malware distribution.

Casky's 323 matched skills leverage Claude's extended reasoning to detect attack patterns across MITRE techniques TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners using Casky would observe detection signals including: unauthenticated HTTP requests to plugin handlers lacking authorization tokens, POST parameters containing unescaped HTML/JavaScript payloads being stored directly to the database without sanitization, and suspicious post creation events from external or unexpected sources. The platform's security skills would flag anomalous patterns such as posts authored by system or default accounts when no legitimate admin activity occurred, JavaScript injection attempts in post content fields, and API interactions occurring without proper authentication headers. These findings help practitioners identify both active exploitation attempts and post-compromise artifacts indicating successful malicious post publication.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

323 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-88903.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-88903

Casky has 323 skills that investigate the attack patterns behind CVE-2026-88903. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn