Skip to content
Fencer Intel
low 3.7

CVE-2022-29254 json

Failed payment recorded has completed in silverstripe/silverstripe-omnipay

published 4y ago modified 4mo ago also GHSA-48f2-m7jg-866x , EUVD-2022-5918

cvss
3.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits
0
none known

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.

Patch / fix

  • packagist silverstripe/silverstripe-omnipay 2.5.2, 3.0.2, 3.1.4, 3.2.1
  • silverstripe silverstripe-omnipay 2.5.2, 3.0.2, 3.1.4, 3.2.1

Is CVE-2022-29254 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:P/I:P/A:N
GitHub 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist silverstripe/silverstripe-omnipay
<2.5.2
>=3.0.0, <3.0.2
>=3.1.0, <3.1.4
>=3.2.0, <3.2.1
2.5.2
3.0.2
3.1.4
3.2.1

Affected products

  • silverstripe silverstripe-omnipay

Classification

Weakness
  • CWE-436 Interpretation Conflict
  • CWE-437 Incomplete Model of Endpoint Features

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.