CVE-2026-103324 Cardinity CVE debrief

Who should care

Defenders responsible for WordPress installations using the Cardinity Payment Gateway for WooCommerce plugin, particularly those managing e-commerce sites, should assess exposure and prioritize updates to mitigate potential risks.

Why it matters

CVE-2026-103324 is a medium-severity vulnerability in the Cardinity Payment Gateway for WooCommerce plugin for WordPress. It allows unauthenticated attackers to forge payment notifications due to an empty default secret used for signing these notifications. Defenders should verify payment notification authenticity and update to version 3.4.2 or later. This vulnerability could lead to unauthorized changes in order payment statuses, potentially impacting financial transactions.

• Potential unauthorized modification of order payment statuses
• Possible financial impact due to unauthorized order changes
• Need for verification of payment notification authenticity
• Priority for updating to a fixed version of the plugin

Technical summary

The Cardinity Payment Gateway for WooCommerce plugin for WordPress does not properly verify the authenticity of payment notifications it receives, as the secret used to sign them is empty by default. This allows unauthenticated attackers to forge an approved-payment notification and mark arbitrary orders as paid, or force them to failed. Defenders should prioritize verifying the authenticity of payment notifications and updating to version 3.4.2 or later of the Cardinity Payment Gateway for WooCommerce plugin. The vulnerability impacts financial transactions and requires verification of payment notification authenticity.

Defensive priority

Defenders should prioritize verifying the authenticity of payment notifications and updating to version 3.4.2 or later of the Cardinity Payment Gateway for WooCommerce plugin.

Recommended defensive actions

• Verify the authenticity of payment notifications
• Update to version 3.4.2 or later of the Cardinity Payment Gateway for WooCommerce plugin
• Monitor for suspicious payment activity
• 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 CVE record and source item provide details on the vulnerability, including its description and affected versions. However, additional information from other sources may be necessary to fully assess the vulnerability.

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.