WordPress Download Monitor Plugin Stored XSS via postMessage

The Download Monitor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Cross-Origin postMessage to Admin Editor in all versions up to, and including, 5.2.10 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the attacker to trick an authenticated Administrator into visiting an attacker-controlled page that targets an open Download edit screen, after which the payload is persisted unfiltered via the Administrator's unfiltered_html capability and later emitted verbatim to the frontend by the [download_data] shortcode's unescaped post_content render path.

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 Download Monitor plugin for WordPress versions up to 5.2.10 contains a Stored Cross-Site Scripting (XSS) vulnerability that allows unauthenticated attackers to inject malicious scripts into admin pages through Cross-Origin postMessage exploitation. This vulnerability is particularly dangerous because injected scripts persist in the database and execute whenever an authenticated administrator accesses the compromised page, potentially leading to account takeover, credential theft, or further malware distribution. Organizations running WordPress sites with this plugin installed face significant risk, especially those with limited administrative oversight or security controls around plugin updates.

Casky's 323 mapped security skills leverage Claude AI's extended reasoning to detect the attack chain across MITRE ATT&CK techniques TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners using Casky would identify findings such as: (1) suspicious postMessage event listeners in admin-context JavaScript that lack origin validation, (2) input data flowing directly into DOM operations without sanitization checks, (3) patterns of Cross-Origin requests attempting to manipulate admin editor interfaces, and (4) payloads designed to establish persistence through stored XSS patterns. The platform's skill coverage would surface both the vulnerable code patterns during assessment and the behavioral indicators that distinguish this exploit from legitimate admin functionality, enabling practitioners to validate whether their WordPress installations are exploitable before attackers weaponize social engineering tactics to deliver the attack.

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-100182.

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-100182

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

Run the skill that detects this →

X Instagram LinkedIn