CVEvulnerability

CVE-2022-29254

6.5 MEDIUM Published 2022-06-09 Modified 2026-06-17 Official page ↗
Status
Modified
Published
2022-06-09
Last modified
2026-06-17
Assigner
[email protected]
CVSS 3.1 ([email protected])
3.7 LOW — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
CVSS 3.1 ([email protected])
6.5 MEDIUM — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
CVSS 2.0 ([email protected])
5.8 MEDIUM — AV:N/AC:M/Au:N/C:P/I:P/A:N
Weaknesses
CWE-436

Description

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 configurations

• silverstripe silverstripe-omnipay (< 2.5.2) • silverstripe silverstripe-omnipay (>= 3.0.0 < 3.0.2) • silverstripe silverstripe-omnipay (>= 3.1.0 < 3.1.4) • silverstripe silverstripe-omnipay (>= 3.2.0 < 3.2.1)

Related

Weakness · CWE (1)

  • CWE-436 Interpretation Conflict weakness

References