WordPress Autopay Plugin Unauthenticated Stored XSS in Checkout

The Autopay WordPress plugin before 5.0.1 does not perform any capability or nonce check before saving a styling option from a public request, and does not escape that value when it is later output on the checkout page, allowing unauthenticated attackers to store JavaScript that executes in the browser of any user, including administrators, who loads the checkout page.

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

The Autopay WordPress plugin before version 5.0.1 contains a critical stored cross-site scripting (XSS) vulnerability that allows unauthenticated attackers to inject malicious JavaScript into the checkout page. The vulnerability exists because the plugin fails to validate user permissions (capability checks) or verify request authenticity (nonce validation) before accepting styling option inputs from public requests. Additionally, the plugin does not sanitize or escape these values when rendering them on the checkout page. This creates a persistent attack vector where an attacker can inject malicious code once, and it executes in the browsers of all users—including administrators—who subsequently visit the checkout page. Any WordPress installation running Autopay before 5.0.1 is affected, making this particularly dangerous for e-commerce sites that depend on checkout page functionality.

Casky's 322 matching skills leverage Claude AI's extended reasoning to detect the attack patterns mapped to MITRE ATT&CK techniques TA0001 (Reconnaissance) and TA0043 (Reconnaissance). Practitioners using Casky would identify this vulnerability through detection of CWE-79 patterns: the absence of capability/nonce verification (indicating broken access controls during the "Initial Access" phase) combined with insufficient output encoding (enabling the "Execution" phase of the attack chain). When analyzing plugin behavior or scanning WordPress configurations, Casky would flag unauthenticated parameters directly influencing stored database values without validation, and unescaped variable outputs in user-facing templates. Security teams would see findings highlighting the gap between input acceptance and output encoding, enabling them to prioritize patching or implement Web Application Firewall (WAF) rules to block malicious styling submissions 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 →

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

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

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

Run the skill that detects this →

X Instagram LinkedIn