Welcart WordPress Plugin Stored XSS via Payment Parameter

The Welcart e-Commerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'gid' parameter in all versions up to, and including, 2.12.5 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. The payload is staged by an unauthenticated visitor who forges the ROBOT PAYMENT browser-return request, storing the malicious gid value in order metadata; the script then fires when an administrator opens that order in the WordPress admin panel.

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

Welcart, a popular e-commerce plugin for WordPress, contains a stored cross-site scripting (XSS) vulnerability in versions up to 2.12.5 that allows unauthenticated attackers to inject malicious scripts through the 'gid' parameter in forged ROBOT PAYMENT browser-return requests. Because the vulnerability is stored rather than reflected, the injected payload persists in the application and executes whenever any user accesses the affected page, creating a persistent threat. This impacts all WordPress sites running vulnerable Welcart versions and their visitors, making it a high-severity issue affecting both merchants and customers in the e-commerce ecosystem.

Casky's 323 mapped skills detect this attack pattern by correlating indicators across MITRE ATT&CK's Initial Access (TA0001) and Persistence (TA0043) techniques. Practitioners using Casky would identify suspicious findings including: detection of unsanitized input flowing into 'gid' parameters without proper output encoding (CWE-79 signature), JavaScript payloads embedded in payment callbacks, stored malicious content in the application database, and script execution in user sessions triggered by page access. Claude's extended reasoning capabilities help practitioners understand the attack chain—how an unauthenticated visitor crafts a malicious payment request, how insufficient sanitization allows storage of the payload, and how persistence is achieved once the script executes in victim browsers. This enables security teams to prioritize remediation and understand the full scope of compromise beyond simple vulnerability scanning.

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

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

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

Run the skill that detects this →

X Instagram LinkedIn