Elementor Free Builder Plugin Stored XSS in Contact Forms

The Free Builder for Elementor WordPress plugin before 1.6.7 does not sanitise submitted contact form field values before storing them and outputting them in the admin dashboard, allowing unauthenticated attackers to perform Stored Cross-Site Scripting attacks that execute when a logged-in administrator views the form submissions.

Casky was already ahead

This CVE exploits attack patterns that Casky's 322matched 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

This vulnerability is a Stored Cross-Site Scripting (XSS) flaw in the Free Builder for Elementor WordPress plugin versions before 1.6.7. The plugin fails to sanitize user-submitted contact form field values before storing them in the database and displaying them in the WordPress admin dashboard. An unauthenticated attacker can inject malicious JavaScript code through form submissions, which then executes in the browser of any logged-in administrator viewing those submissions. This is particularly dangerous because it affects a widely-used page builder plugin, potentially impacting thousands of WordPress sites. Administrators have no visibility that the form data is unsafe, making them unknowing victims when they review submissions. The attack requires no authentication, lowering the barrier for exploitation significantly.

Casky's skill mapping identifies this vulnerability through detection patterns aligned with MITRE ATT&CK's Initial Access (TA0001) and Persistence (TA0043) tactics. Practitioners using Casky's 322 matching skills would observe findings flagging: (1) input validation gaps in form handlers lacking sanitization functions, (2) output encoding failures where user-controlled data reaches admin pages without escaping, and (3) execution flow analysis showing how unsanitized POST parameters flow directly to database storage and HTML rendering. Claude's extended reasoning would correlate the CWE-79 (Improper Neutralization of Input During Web Page Generation) patterns with the specific plugin code, highlighting the absence of WordPress sanitization functions like `sanitize_text_field()` and escaping functions like `esc_html()`. The findings would surface the admin context execution risk, enabling practitioners to prioritize patching and implement input validation controls before attackers weaponize contact form submissions against their administrative users.

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 →

322 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-11767.

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

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

Run the skill that detects this →

X Instagram LinkedIn