# CVE-2022-29254: Failed payment recorded has completed in silverstripe/silverstripe-omnipay > Attackers can prematurely mark failed payments as completed by exploiting exposed payment identifiers in specific Omnipay gateways. - **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 6 Jun 2022 - **Updated:** 23 Apr 2025 - **Also known as:** GHSA-48f2-m7jg-866x ## What is CVE-2022-29254? CVE-2022-29254 is a low-severity vulnerability in silverstripe-omnipay, published on 6 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-436 (Interpretation Conflict) ## Which versions are affected by CVE-2022-29254? 8 open source packages ship an affected version, including silverstripe/silverstripe-omnipay. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `silverstripe/silverstripe-omnipay` | Packagist | All versions | 2.5.2 | | `silverstripe/silverstripe-omnipay` | Packagist | All versions | 2.5.2 | | `silverstripe/silverstripe-omnipay` | Packagist | From 3.0.0 | 3.0.2 | | `silverstripe/silverstripe-omnipay` | Packagist | From 3.0.0 | 3.0.2 | | `silverstripe/silverstripe-omnipay` | Packagist | From 3.1.0 | 3.1.4 | | `silverstripe/silverstripe-omnipay` | Packagist | From 3.1.0 | 3.1.4 | | `silverstripe/silverstripe-omnipay` | Packagist | From 3.2.0 | 3.2.1 | | `silverstripe/silverstripe-omnipay` | Packagist | From 3.2.0 | 3.2.1 | Products: Silverstripe Silverstripe-Omnipay. ## How do I fix CVE-2022-29254? Upgrade silverstripe/silverstripe-omnipay to a fixed version for your release line: 2.5.2, 3.0.2, 3.1.4 or 3.2.1. ## Is CVE-2022-29254 being exploited? There is no known exploitation of CVE-2022-29254 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-29254 and fix it if it is affected. What it is: CVE-2022-29254 is a low-severity vulnerability in silverstripe-omnipay, published on 6 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-29254 in the wild and no public exploit code. Affected packages and fixed versions: - silverstripe/silverstripe-omnipay (Packagist): affected all versions; fixed in 2.5.2 - silverstripe/silverstripe-omnipay (Packagist): affected all versions; fixed in 2.5.2 - silverstripe/silverstripe-omnipay (Packagist): affected from 3.0.0; fixed in 3.0.2 - silverstripe/silverstripe-omnipay (Packagist): affected from 3.0.0; fixed in 3.0.2 - silverstripe/silverstripe-omnipay (Packagist): affected from 3.1.0; fixed in 3.1.4 - silverstripe/silverstripe-omnipay (Packagist): affected from 3.1.0; fixed in 3.1.4 - silverstripe/silverstripe-omnipay (Packagist): affected from 3.2.0; fixed in 3.2.1 - silverstripe/silverstripe-omnipay (Packagist): affected from 3.2.0; fixed in 3.2.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-29254/ (Markdown: https://insights.sbomify.com/CVE-2022-29254/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-29254 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-29254 - OSV: https://osv.dev/vulnerability/CVE-2022-29254 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-29254/ Summaries are generated and may contain mistakes; the official description above is the record.