WordPress Fancy Product Designer Stored XSS via Order Meta

The Fancy Product Designer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'productTitle' in '_fpd_data' Order Item Meta in all versions up to, and including, 6.5.2 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 fpd_save_order AJAX action is registered for unauthenticated users via wp_ajax_nopriv_fpd_save_order with no nonce or capability check, and the strip_tags() sanitization applied at save time is bypassed by submitting JSON unicode escape sequences (e.g. \u003c, \u003e), which json_decode() silently converts back to literal angle brackets when the order is rendered in the admin view.

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 Fancy Product Designer plugin for WordPress contains a Stored Cross-Site Scripting (XSS) vulnerability in versions up to 6.5.2, where user-supplied input in the 'productTitle' field within order item metadata is not properly sanitized or escaped before being displayed. This vulnerability is particularly dangerous because it allows unauthenticated attackers to inject malicious scripts that persist in the database and execute whenever any user—including administrators—views an affected page. The vulnerability is exploitable through the fpd_save_order AJAX action, which is explicitly registered for unauthenticated users via wp_ajax_nopriv_fpd_save, creating a low-barrier attack surface. Any WordPress site running this plugin is vulnerable, affecting not just the site owner but all users who interact with affected product pages or orders.

Casky's 754 security skills, powered by Claude's extended reasoning capabilities, would map this vulnerability across both Initial Access (TA0001) and Execution (TA0043) techniques. Practitioners using Casky would identify attack patterns including insufficient input validation (CWE-79 manifestation), improper AJAX permission handling, and database-persisted payload injection. The platform's skill set would detect the specific risk chain: unauthenticated endpoint → unsanitized user input → stored malicious script → automatic execution on page load. Findings would highlight the critical combination of weak access controls (allowing wp_ajax_nopriv registration) and output encoding failures, helping practitioners prioritize patching this plugin and implementing Web Application Firewall (WAF) rules to detect script injection attempts in product title parameters.

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

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

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

Run the skill that detects this →

X Instagram LinkedIn