Every CVE Search/ Get API key

CVE-2022-29254

Failed payment recorded has completed in silverstripe/silverstripe-omnipay

3.7 LowFix available

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.

Attack profile

How easy it is to exploit

Attack vector
Network
Complexity
High
Privileges needed
None
User interaction
None

What an attacker can affect

Confidentiality
None
Integrity
Low
Availability
None

Exploit likelihood

0.68%Down 0.2 points since Jun 7, 2022
90%50%10%1%

What each source reports

CVE List Score used 3.7

Failed payment recorded has completed in silverstripe/silverstripe-omnipay

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.

Record
CVE-2022-29254
CVSS 3.1
3.7 LowCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Weakness
CWE-436
Updated
2026-11-02
EUVDEUVD-2022-5918 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.

Record
EUVD-2022-5918
CVSS 3.1
3.7 LowCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Updated
2026-11-02
GitHub AdvisoriesGHSA-48f2-m7jg-866x 3.7

Failed payment recorded has completed in Silverstripe Omnipay

Impact

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.

Patches

The following versions have been patched to fix this issue:

  • 2.5.2
  • 3.0.2
  • 3.1.4
  • 3.2.1

Workarounds

There are no known workarounds for this vulnerability.

References

N/A.

For more information

If you have any questions or comments about this advisory:

Record
GHSA-48f2-m7jg-866x
CVSS 3.1
3.7 LowCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Weakness
CWE-436, CWE-437
Updated
2026-11-02
NVD 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.

Record
CVE-2022-29254
CVSS 3.1
3.7 LowCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
CVSS 3.1
6.5 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
CVSS 2.0
5.8 MediumAV:N/AC:M/Au:N/C:P/I:P/A:N
Weakness
CWE-436
Updated
2026-11-02
OSV 3.7

Failed payment recorded has completed in silverstripe/silverstripe-omnipay

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.

Record
CVE-2022-29254
CVSS 3.1
3.7 LowCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Weakness
CWE-436
Updated
2026-11-02
OSVGHSA-48f2-m7jg-866x 3.7

Failed payment recorded has completed in Silverstripe Omnipay

Impact

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.

Patches

The following versions have been patched to fix this issue:

  • 2.5.2
  • 3.0.2
  • 3.1.4
  • 3.2.1

Workarounds

There are no known workarounds for this vulnerability.

References

N/A.

For more information

If you have any questions or comments about this advisory:

Record
GHSA-48f2-m7jg-866x
CVSS 3.1
3.7 LowCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Weakness
CWE-436, CWE-437
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
silverstripe/silverstripe-omnipay
Packagist
 before 2.5.2
2.5.2
silverstripe/silverstripe-omnipay
Packagist
 3.0.0 up to 3.0.2
3.0.2
silverstripe/silverstripe-omnipay
Packagist
 3.1.0 up to 3.1.4
3.1.4
silverstripe/silverstripe-omnipay
Packagist
 3.2.0 up to 3.2.1
3.2.1
silverstripe/silverstripe-omnipay
Packagist
 before 2.5.2, plus listed versions
1.0.01.0.0-beta11.0.11.0.21.1.0
Show 10 moreShow less
1.1.11.3.02.0-alpha2.0.02.1.02.2.02.3.02.4.02.5.02.5.1
2.5.2
silverstripe/silverstripe-omnipay
Packagist
 3.0.0 up to 3.0.2, plus listed versions
3.0.1
3.0.2
silverstripe/silverstripe-omnipay
Packagist
 3.1.0 up to 3.1.4, plus listed versions
3.1.13.1.23.1.3
3.1.4

History

History
RecordedChangedSources
first indexedCVE List, EUVD, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2022-29254 is a low vulnerability (CVSS 3.7) in Silverstripe Silverstripe-omnipay, published June 6, 2022. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.68%, the 52nd percentile. Fixed in silverstripe/silverstripe-omnipay 2.5.2.

References

Show 4 moreShow less
Pages All vulnerabilities Browse Docs Sources Guide Get API key
MoveEnter Open