WordPress security changelog
UNKNOWN CVE-2026-12966 Received

Direct Payments lets visitors forge payment state and proof on other orders

Direct Payments for WooCommerce before 2.5.3 exposes several unauthenticated AJAX handlers that modify a selected order without confirming that the requester owns it. A visitor can target another customer's WooCommerce order, mark it as payment sent, overwrite the payment-method label and attach a forged payment-proof file. The published record does not disclose the action names, order identifier, status and label fields, upload parameter or update functions.

CVE / CNA score Pending The CVE record has not published a CNA CVSS assessment.
NVD score Pending NVD has not published its own CVSS assessment.
Component
Direct Payments for WooCommerce
Plugin slug
direct-payments-for-woocommerce
Affected
< 2.5.3
Safe version
2.5.3
Published
Aug 01, 2026
Weakness
Not assigned

This CVE was published Aug 01, 2026 and is one of 1 known issue for this plugin.

Update, patch or deactivate.

Update Direct Payments for WooCommerce to 2.5.3 or later. Reconcile payment-sent orders with bank or processor records before fulfillment, review unauthenticated AJAX traffic and uploaded proof files, restore altered metadata, and remove malicious uploads.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

The Direct Payments for WooCommerce WordPress plugin before 2.5.3 does not verify that the requester owns the targeted WooCommerce order in several unauthenticated AJAX handlers before changing its status and overwriting its payment metadata, allowing unauthenticated attackers to tamper with other customers' orders, including forging a "payment sent" state, overwriting the payment-method label, and attaching forged payment-proof files.

Primary and upstream sources