The Casso Flow WordPress plugin before 4.2.0 does not properly authenticate incoming bank-transfer payment
Source GCVE Database
Not known to be exploited : upgrade to 4.2.0 soon.
Data as of 28 Oct 2026, 07:29 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in 4.2.0
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Casso Flow (WordPress plugin) to 4.2.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Casso Flow | Affected
| Fixed in
|
AI-suggested
Upgrade the Casso Flow WordPress plugin to version 4.2.0 or later where this authentication issue is resolved. No other mitigation details are provided.
Description
The Casso Flow WordPress plugin versions before 4.2.0 have a vulnerability where incoming bank-transfer payment notifications are not properly authenticated. The token used for verification is empty by default, enabling unauthenticated attackers to forge notifications and mark any pending WooCommerce order as paid regardless of the actual payment method.