Silverstripe Omnipay
Approved changes feed: RSS · Atom
cpe:2.3:a:silverstripe:silverstripe-omnipay:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Silverstripe (fb3ee4e6-70c4-5017-82a7-81441bb33bd1) |
|---|---|
| Product | Silverstripe Omnipay (068ec75f-7949-5cd9-9c13-2b36ef6d8f3e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/silverstripe/silverstripe-omnipay |
purl2cpe | 2026-06-01 10:14:20.878286 |
pkg:github/thephpleague/omnipay |
purl2cpe | 2026-06-01 10:14:20.878289 |
pkg:sourceforge/omnipay.mirror |
purl2cpe | 2026-06-01 10:14:20.878291 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-29254 |
vulnerable | 2026-06-03 14:46:57.498963 |
Failed payment recorded has completed in silverstripe/silverstripe-omnipay
LOW (3.7)
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.
Published: 2022-06-06T19:35:10.000Z
Updated: 2025-04-23T18:19:05.162Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.