CVE-2022-29254: Failed payment recorded has completed in silverstripe/silverstripe-omnipay
silverstripe · silverstripe-omnipay
Affected: silverstripe-omnipay · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 52% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- silverstripe · silverstripe-omnipay< 2.5.2; >= 3.0.0, < 3.0.2; >= 3.1.0, < 3.1.4; >= 3.2.0, < 3.2.1
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- silverstripe
- Published
- June 2022
CoverageNo articles yet
No CyberSIXT article names CVE-2022-29254 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.