{"answers":{"affected":"8 open source packages ship an affected version, including silverstripe/silverstripe-omnipay. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-29254 in the wild and no public exploit code.","fix":"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.","what":"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."},"fix_prompt":"Check this codebase for CVE-2022-29254 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2022-29254 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- silverstripe/silverstripe-omnipay (Packagist): affected all versions; fixed in 2.5.2\n- silverstripe/silverstripe-omnipay (Packagist): affected all versions; fixed in 2.5.2\n- silverstripe/silverstripe-omnipay (Packagist): affected from 3.0.0; fixed in 3.0.2\n- silverstripe/silverstripe-omnipay (Packagist): affected from 3.0.0; fixed in 3.0.2\n- silverstripe/silverstripe-omnipay (Packagist): affected from 3.1.0; fixed in 3.1.4\n- silverstripe/silverstripe-omnipay (Packagist): affected from 3.1.0; fixed in 3.1.4\n- silverstripe/silverstripe-omnipay (Packagist): affected from 3.2.0; fixed in 3.2.1\n- silverstripe/silverstripe-omnipay (Packagist): affected from 3.2.0; fixed in 3.2.1\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-29254/ (Markdown: https://insights.sbomify.com/CVE-2022-29254/index.md)","id":"CVE-2022-29254","markdown":"https://insights.sbomify.com/CVE-2022-29254/index.md","name":"CVE-2022-29254","record":{"aliases":["GHSA-48f2-m7jg-866x"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"SilverStripe payment plugin","requires_auth":"none","summary":"Attackers can prematurely mark failed payments as completed by exploiting exposed payment identifiers in specific Omnipay gateways.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"silverstripe-omnipay","vendor":"silverstripe"}],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-436","name":"Interpretation Conflict"}],"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.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Failed payment recorded has completed in silverstripe/silverstripe-omnipay","id":"CVE-2022-29254","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"business_logic","year":"2022"},"n_packages":8,"n_references":2,"next":{"headline":"Multiple evaluation of contract address in call in vyper","id":"CVE-2022-29255"},"packages":[{"ecosystem":"Packagist","fixed":["2.5.2"],"introduced":["0"],"last_affected":[],"package":"silverstripe/silverstripe-omnipay","purl":null,"source":"GHSA-48f2-m7jg-866x"},{"ecosystem":"Packagist","fixed":["2.5.2"],"introduced":["0"],"last_affected":[],"package":"silverstripe/silverstripe-omnipay","purl":"pkg:composer/silverstripe/silverstripe-omnipay","source":"GHSA-48f2-m7jg-866x"},{"ecosystem":"Packagist","fixed":["3.0.2"],"introduced":["3.0.0"],"last_affected":[],"package":"silverstripe/silverstripe-omnipay","purl":null,"source":"GHSA-48f2-m7jg-866x"},{"ecosystem":"Packagist","fixed":["3.0.2"],"introduced":["3.0.0"],"last_affected":[],"package":"silverstripe/silverstripe-omnipay","purl":"pkg:composer/silverstripe/silverstripe-omnipay","source":"GHSA-48f2-m7jg-866x"},{"ecosystem":"Packagist","fixed":["3.1.4"],"introduced":["3.1.0"],"last_affected":[],"package":"silverstripe/silverstripe-omnipay","purl":null,"source":"GHSA-48f2-m7jg-866x"},{"ecosystem":"Packagist","fixed":["3.1.4"],"introduced":["3.1.0"],"last_affected":[],"package":"silverstripe/silverstripe-omnipay","purl":"pkg:composer/silverstripe/silverstripe-omnipay","source":"GHSA-48f2-m7jg-866x"},{"ecosystem":"Packagist","fixed":["3.2.1"],"introduced":["3.2.0"],"last_affected":[],"package":"silverstripe/silverstripe-omnipay","purl":null,"source":"GHSA-48f2-m7jg-866x"},{"ecosystem":"Packagist","fixed":["3.2.1"],"introduced":["3.2.0"],"last_affected":[],"package":"silverstripe/silverstripe-omnipay","purl":"pkg:composer/silverstripe/silverstripe-omnipay","source":"GHSA-48f2-m7jg-866x"}],"prev":{"headline":"Path Traversal in XWiki Platform","id":"CVE-2022-29253"},"products":["silverstripe-omnipay"],"published":"2022-06-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["silverstripe"]},"summary":"Attackers can prematurely mark failed payments as completed by exploiting exposed payment identifiers in specific Omnipay gateways.","url":"https://insights.sbomify.com/CVE-2022-29254/"}