CVE-2026-103382

Casso Auto-confirm Bank Transfer < 4.2.0 - Unauthenticated WooCommerce Order Payment Confirmation

Published Oct 28, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
The Casso Flow WordPress plugin before 4.2.0 does not properly authenticate incoming bank-transfer payment notifications, as the token used to verify them is empty on a default installation, allowing unauthenticated attackers to forge a notification and mark any pending WooCommerce order as paid, regardless of its payment method.

Analysis

AI-generated

Technical impact

The vulnerability in the Casso Flow WordPress plugin allows an attacker to forge bank‑transfer payment notifications because the verification token is empty by default. An unauthenticated attacker can send a crafted notification to the shop, causing any pending WooCommerce order to be marked as paid regardless of the actual payment method. This can lead to fraudulent transactions and financial loss, demonstrating failures in authentication mechanisms (CWE-284).

Affected Systems

The issue affects installations of the Casso Flow WordPress plugin that are before version 4.2.0 and that use WooCommerce for order management. Any site using this plugin and not up‑to‑date with the fix is susceptible.

Risk and Exploitability

The CVSS score of 5.3 indicates a medium severity vulnerability. The EPSS score is < 1%, suggesting a low probability of exploitation in the wild. The vulnerability is not listed in the CISA KEV catalog. Because the token used for bank‑transfer notifications is empty by default, any attacker can send a crafted notification to the shop and mark any pending WooCommerce order as paid, regardless of its payment method. No additional authentication or privileges are required, so the attack surface is wide and the risk is significant for any site using an outdated version of the Casso Flow plugin.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the plugin update to version 4.2.0 or later, which removes the empty token issue
  • Configure the payment notification endpoint so that it requires a non‑empty, secret token or other authentication mechanism before accepting status changes
  • Disable or restrict external notification traffic to the WooCommerce order status endpoint, and monitor order logs for unexpected paid status changes

Generated by OpenCVE AI on October 28, 2026 at 21:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions casso Auto-confirm Bank Transfer
Vendors & Products Wordpress-extensions
Wordpress-extensions casso Auto-confirm Bank Transfer
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-287
Type Values Removed Values Added
Weaknesses CWE-284
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}

Type Values Removed Values Added
Weaknesses CWE-287
Type Values Removed Values Added
Description The Casso Flow WordPress plugin before 4.2.0 does not properly authenticate incoming bank-transfer payment notifications, as the token used to verify them is empty on a default installation, allowing unauthenticated attackers to forge a notification and mark any pending WooCommerce order as paid, regardless of its payment method.
Title Casso Auto-confirm Bank Transfer < 4.2.0 - Unauthenticated WooCommerce Order Payment Confirmation
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Oct 28, 2026, 5:58 PM
Reserved
Sep 30, 2026, 1:18 PM
Status
Deferred
Published
Oct 28, 2026, 6:16 AM
Modified
Oct 28, 2026, 6:17 PM