WooCommerce Plugin Stored XSS via Unsanitized Multipart Fields

The WPC Product Options for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via wpcpo-* Array Key via Multipart Field Name in all versions up to, and including, 4.0.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. This is exploitable via guest checkout without authentication because the malicious payload is embedded in a multipart Content-Disposition field name beginning with 'wpcpo-', which PHP's RFC1867 parser preserves byte-for-byte and stores into order item meta.

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 WPC Product Options for WooCommerce plugin contains a stored cross-site scripting (XSS) vulnerability affecting all versions through 4.0.5. Attackers can inject malicious JavaScript through the wpcpo-* array keys in multipart form field names during guest checkout, bypassing authentication requirements entirely. When legitimate users access product pages containing injected content, the malicious scripts execute in their browsers with full session privileges. This vulnerability impacts any WordPress e-commerce site using this plugin, potentially compromising customer data, session tokens, and enabling credential theft or malware distribution at scale.

Casky's 323 matched skills leverage Claude's extended reasoning to detect the attack patterns mapped to TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners using Casky would identify suspicious patterns including: unauthenticated POST requests with unusual multipart field naming conventions containing script tags, base64-encoded payloads, or event handlers in the wpcpo-* parameters; stored XSS indicators in database queries showing persistence of unsanitized input in product metadata; and DOM-based execution signatures where user-supplied data flows directly to innerHTML or eval contexts without sanitization. The platform would surface these findings alongside specific remediation guidance tied to input validation, output encoding, and content security policy implementation across the vulnerable code paths.

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

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

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

Run the skill that detects this →

X Instagram LinkedIn