WordPress Plugin Stores Malicious Scripts in User Posts

The User Submitted Posts – Enable Users to Submit Posts from the Front End plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'user-submitted-content' parameter in all versions up to, and including, 20260916 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. On a default installation the submitted post is held as Pending and requires admin approval before the payload is reachable by other visitors; however, if the plugin's "publish immediately" option is enabled, no approval step exists and the stored payload becomes live without any moderator interaction.

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 User Submitted Posts plugin for WordPress contains a Stored DOM-Based Cross-Site Scripting (XSS) vulnerability that allows unauthenticated attackers to inject arbitrary JavaScript through the 'user-submitted-content' parameter. Because the plugin fails to properly sanitize user input and escape output, malicious scripts become permanently stored in submitted posts. When any visitor accesses a page containing injected content, the malicious code executes in their browser with their privileges. This affects any WordPress site running the vulnerable plugin versions up to 20260916, creating a persistent threat vector that compromises user sessions, steals credentials, and enables account takeover without requiring authentication.

Casky's 323 matching security skills leverage Claude AI's extended reasoning to detect the attack patterns underlying this vulnerability across MITRE ATT&CK's Initial Access (TA0001) and Reconnaissance (TA0043) techniques. Practitioners using Casky will observe detections mapping to credential harvesting patterns, malicious script injection signatures, and DOM manipulation indicators. The platform's skill mapping identifies how attackers leverage CWE-79 weaknesses to achieve Initial Access through social engineering via stored content, then use Reconnaissance techniques to profile victim interactions with compromised posts. Security teams see findings that correlate unsanitized user input flows, missing output encoding controls, and execution context violations—enabling them to pinpoint vulnerable code patterns and prioritize remediation across their WordPress infrastructure before exploitation occurs.

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

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

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

Run the skill that detects this →

X Instagram LinkedIn