CVE-2026-84281 radykal CVE debrief

Who should care

Defenders responsible for WordPress installations with the Fancy Product Designer plugin should assess exposure and prioritize verification and remediation. This includes reviewing the plugin version, implementing additional input sanitization and output escaping, and monitoring for suspicious activity related to the fpd_save_order AJAX action.

Why it matters

The Fancy Product Designer plugin for WordPress has a high-severity Stored Cross-Site Scripting vulnerability, allowing unauthenticated attackers to inject arbitrary web scripts. Defenders should prioritize verification and remediation to prevent exploitation.

• Unauthenticated attackers can inject arbitrary web scripts
• Injected scripts execute when a user accesses an injected page
• Defenders must verify and update the Fancy Product Designer plugin to prevent exploitation
• Remediation priority is high due to the high CVSS score of 7.2

Technical summary

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. The fpd_save_order AJAX action is registered for unauthenticated users with no nonce or capability check, allowing for the bypass of strip_tags() sanitization by submitting JSON unicode escape sequences. This allows unauthenticated attackers to inject arbitrary web scripts, which execute when a user accesses an injected page. The vulnerability is caused by insufficient input sanitization and output escaping.

Defensive priority

Defenders should prioritize verifying and updating the Fancy Product Designer plugin to prevent exploitation.

Recommended defensive actions

• Verify the Fancy Product Designer plugin version and update to a patched version if necessary
• Implement additional input sanitization and output escaping for the plugin
• Monitor for suspicious activity related to the fpd_save_order AJAX action
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is caused by insufficient input sanitization and output escaping. The fpd_save_order AJAX action is registered for unauthenticated users with no nonce or capability check, allowing for the bypass of strip_tags() sanitization by submitting JSON unicode escape sequences.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.