Failed payment recorded has completed in silverstripe/silverstripe-omnipay
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.5.2, 3.0.2, 3.1.4, 3.2.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
silverstripe-omnipay is a SilverStripe integration with Omnipay PHP payments library. For a subset of Omnipay gateways (those that use intermediary states like `isNotification()` or `isRedirect()`), if the payment identifier or success URL is exposed it is possible for payments to be prematurely marked as completed without payment being taken. This is mitigated by the fact that most payment gateways hide this information from users, however some issuing banks offer flawed 3DSecure implementations that may inadvertently expose this data. The following versions have been patched to fix this issue: `2.5.2`, `3.0.2`, `3.1.4`, and `3.2.1`. There are no known workarounds for this vulnerability.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- silverstripe silverstripe-omnipay
fixed in 2.5.2; From 3.0.0 · fixed in 3.0.2; From 3.1.0 · fixed in 3.1.4; From 3.2.0 · fixed in 3.2.1
- silverstripe/silverstripe-omnipayPackagist
fixed in 2.5.2
- silverstripe/silverstripe-omnipayPackagist
From 3.0.0 · fixed in 3.0.2
- silverstripe/silverstripe-omnipayPackagist
From 3.1.0 · fixed in 3.1.4
- silverstripe/silverstripe-omnipayPackagist
From 3.2.0 · fixed in 3.2.1