Ninja Forms Stored XSS in Legacy Submission Editor

Ninja Forms 3.15.3 stores an anonymous non-RTE textarea value and renders it without safe HTML encoding in the legacy submission editor. An attacker can break out of the textarea with stored script. When an Administrator opens the attacker-known direct submission URL, the script runs in the WordPress admin origin.

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

Ninja Forms versions 3.15.3 and likely earlier contain a stored cross-site scripting (XSS) vulnerability in the legacy submission editor where textarea values are rendered without proper HTML encoding. This vulnerability allows attackers to inject malicious scripts that execute when administrators access submission URLs, compromising the WordPress admin context. The risk is particularly acute because the injection point accepts anonymous submissions—meaning any unauthenticated user can plant the payload—and the execution occurs in the high-privilege administrative origin where the attacker can steal session tokens, modify site content, or create backdoor accounts. Organizations running Ninja Forms for contact forms, applications, or feedback collection are directly affected, especially those with multiple administrator accounts.

Casky's 754 security skills, powered by Claude AI with extended reasoning, detect the attack patterns underlying this vulnerability by mapping to MITRE ATT&CK techniques TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners using Casky would see findings highlighting: (1) unsanitized user input flowing into administrative interfaces—a classic CWE-79 pattern—(2) detection of textarea breakout payloads in form submission logs, and (3) evidence of script execution within the WordPress admin origin indicating privilege escalation. The platform's extended reasoning capability allows it to connect the dots between anonymous submission storage and admin-context execution, surfacing the full attack chain rather than isolated events. Security teams would receive alerts flagging submissions containing HTML/JavaScript entities, unusual iframe or script tag patterns in textarea fields, and browser console activity originating from submission editor URLs—enabling rapid identification and remediation before attackers weaponize stored XSS for persistent admin compromise.

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

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

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

Run the skill that detects this →

X Instagram LinkedIn