Stored XSS in Gravity Forms Click5 CRM Add-on

The click5 CRM add-on to Gravity Forms WordPress plugin through 1.0.3 does not sanitise and escape content submitted through an unauthenticated endpoint before outputting it back in an admin page, leading to Stored XSS which could be used against high privilege users such as admin.

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 click5 CRM add-on for Gravity Forms contains a stored cross-site scripting (XSS) vulnerability that allows attackers to inject malicious scripts through an unauthenticated endpoint. Because the plugin fails to sanitize and escape user-supplied content before displaying it on admin pages, any attacker can submit malicious payloads that persist in the database and execute when administrators access affected pages. This is particularly critical because it targets high-privilege users like site administrators, potentially leading to account compromise, malware distribution, or complete site takeover. Organizations using Gravity Forms with the click5 CRM add-on version 1.0.3 or earlier face significant risk, as the vulnerability requires no authentication and can be exploited remotely.

Casky's skill set, powered by Claude AI with extended reasoning across 754 MITRE ATT&ACK-mapped techniques, detects this vulnerability through patterns aligned with TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners would identify findings related to input validation failures and output encoding gaps—specifically CWE-79 violations where unsanitized data flows from unauthenticated endpoints to admin interfaces. The platform's skills would surface attack chains where threat actors probe for exposed form endpoints (reconnaissance), inject XSS payloads (initial access/execution), and establish persistence through stored scripts targeting privileged users. Security teams would see correlated detection patterns highlighting the endpoint's lack of nonce verification, missing sanitization functions, and improper use of WordPress escaping mechanisms, enabling them to quickly prioritize remediation and implement compensating controls while awaiting patches.

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

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

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

Run the skill that detects this →

X Instagram LinkedIn