CVE-2026-97660 wpclever CVE debrief

Who should care

Defenders responsible for WordPress installations with the WPC Product Options for WooCommerce plugin should assess exposure and prioritize verification and remediation. This includes reviewing the plugin's version, checking for any signs of exploitation, and ensuring that the latest version is installed. Additionally, defenders should monitor for potential XSS attacks and implement additional security measures to prevent exploitation. Security teams and

Why it matters

The WPC Product Options for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting, allowing unauthenticated attackers to inject arbitrary web scripts.

• Defenders must verify and update the WPC Product Options for WooCommerce plugin to prevent potential XSS attacks
• Defenders should monitor for potential XSS attacks
• Defenders should implement additional security measures to prevent exploitation

Technical summary

The WPC Product Options for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via wpcpo-* Array Key in Multipart Field Names in all versions up to, and including, 4.0.5. The vulnerability exists due to insufficient input sanitization and output escaping. This allows unauthenticated attackers to inject arbitrary web scripts, which are executed when a user accesses an affected page. The exploit is particularly dangerous because it can be delivered through guest checkout without authentication, embedding malicious payloads in multipart Content-Disposition field names that PHP preserves and stores. Defenders must prioritize verifying and updating the plugin to prevent potential XSS

Defensive priority

Defenders should prioritize verifying and updating the WPC Product Options for WooCommerce plugin to prevent potential XSS attacks.

Recommended defensive actions

• Verify and update the WPC Product Options for WooCommerce plugin to the latest version.
• Monitor for potential XSS attacks.
• Implement additional security measures to prevent exploitation.
• 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 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. The exploit does not require authentication and can be triggered when a user accesses an injected page. To verify and mitigate this vulnerability, defenders should review the plugin's input sanitization and output escaping mechanisms. They should also monitor for any

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.