{"items":[{"id":"NVI-00006986","kind":"vulnerability","title":"Failed payment recorded has completed in Silverstripe Omnipay","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-48f2-m7jg-866x","CVE-2022-29254"],"plain_summary":"OSV carries this publisher advisory for silverstripe/silverstripe-omnipay, silverstripe/silverstripe-omnipay, silverstripe/silverstripe-omnipay, silverstripe/silverstripe-omnipay. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.5.2 for silverstripe/silverstripe-omnipay. Confirm the publisher’s latest guidance.","source_ids":["sr-ca45c998adae865c5c7d6ffe86fe1fc1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.0.2 for silverstripe/silverstripe-omnipay. Confirm the publisher’s latest guidance.","source_ids":["sr-ca45c998adae865c5c7d6ffe86fe1fc1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.1.4 for silverstripe/silverstripe-omnipay. Confirm the publisher’s latest guidance.","source_ids":["sr-ca45c998adae865c5c7d6ffe86fe1fc1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.2.1 for silverstripe/silverstripe-omnipay. Confirm the publisher’s latest guidance.","source_ids":["sr-ca45c998adae865c5c7d6ffe86fe1fc1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-726aa9b6d9e41f08a4468bbcebeb5fa4"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-06-17T04:39:55.720Z","value":"5.8 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-726aa9b6d9e41f08a4468bbcebeb5fa4"},{"kind":"CVSS","as_of":"2026-06-17T04:39:55.720Z","value":"3.7 LOW (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-726aa9b6d9e41f08a4468bbcebeb5fa4"},{"kind":"CVSS","as_of":"2026-06-17T04:39:55.720Z","value":"6.5 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-726aa9b6d9e41f08a4468bbcebeb5fa4"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-ca45c998adae865c5c7d6ffe86fe1fc1","url":"https://github.com/advisories/GHSA-48f2-m7jg-866x","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-48f2-m7jg-866x","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.666Z"},{"id":"sr-726aa9b6d9e41f08a4468bbcebeb5fa4","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-29254","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2022-29254","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T23:14:26.524Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-ca45c998adae865c5c7d6ffe86fe1fc1"],"technology":"silverstripe/silverstripe-omnipay","known_exclusions":[],"conditions_summary":"### Impact\nFor 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.\n\n### Patches\nThe following versions have been patched to fix this issue:\n\n- `2.5.2`\n- `3.0.2`\n- `3.1.4`\n- `3.2.1`\n\n### Workarounds\nThere are no known workarounds for this vulnerability.\n\n### References\nN/A.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at security@silverstripe.org\n","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 2.5.2"]},{"certainty":"source_listed","source_ids":["sr-ca45c998adae865c5c7d6ffe86fe1fc1"],"technology":"silverstripe/silverstripe-omnipay","known_exclusions":[],"conditions_summary":"### Impact\nFor 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.\n\n### Patches\nThe following versions have been patched to fix this issue:\n\n- `2.5.2`\n- `3.0.2`\n- `3.1.4`\n- `3.2.1`\n\n### Workarounds\nThere are no known workarounds for this vulnerability.\n\n### References\nN/A.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at security@silverstripe.org\n","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.0.2"]},{"certainty":"source_listed","source_ids":["sr-ca45c998adae865c5c7d6ffe86fe1fc1"],"technology":"silverstripe/silverstripe-omnipay","known_exclusions":[],"conditions_summary":"### Impact\nFor 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.\n\n### Patches\nThe following versions have been patched to fix this issue:\n\n- `2.5.2`\n- `3.0.2`\n- `3.1.4`\n- `3.2.1`\n\n### Workarounds\nThere are no known workarounds for this vulnerability.\n\n### References\nN/A.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at security@silverstripe.org\n","public_affected_ranges":["ECOSYSTEM: introduced 3.1.0; fixed 3.1.4"]},{"certainty":"source_listed","source_ids":["sr-ca45c998adae865c5c7d6ffe86fe1fc1"],"technology":"silverstripe/silverstripe-omnipay","known_exclusions":[],"conditions_summary":"### Impact\nFor 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.\n\n### Patches\nThe following versions have been patched to fix this issue:\n\n- `2.5.2`\n- `3.0.2`\n- `3.1.4`\n- `3.2.1`\n\n### Workarounds\nThere are no known workarounds for this vulnerability.\n\n### References\nN/A.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at security@silverstripe.org\n","public_affected_ranges":["ECOSYSTEM: introduced 3.2.0; fixed 3.2.1"]}],"null_published_at":"2026-11-02T20:21:10.327Z","source_updated_at":"2023-11-08T04:09:12.475Z","source_disclosed_at":"2022-06-06T21:24:39.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:41:49.666Z"},{"id":"NVI-00006986","kind":"vulnerability","title":"Failed payment recorded has completed in Silverstripe Omnipay","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-48f2-m7jg-866x","CVE-2022-29254"],"plain_summary":"OSV carries this publisher advisory for silverstripe/silverstripe-omnipay, silverstripe/silverstripe-omnipay, silverstripe/silverstripe-omnipay, silverstripe/silverstripe-omnipay. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.5.2 for silverstripe/silverstripe-omnipay. Confirm the publisher’s latest guidance.","source_ids":["sr-ca45c998adae865c5c7d6ffe86fe1fc1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.0.2 for silverstripe/silverstripe-omnipay. Confirm the publisher’s latest guidance.","source_ids":["sr-ca45c998adae865c5c7d6ffe86fe1fc1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.1.4 for silverstripe/silverstripe-omnipay. Confirm the publisher’s latest guidance.","source_ids":["sr-ca45c998adae865c5c7d6ffe86fe1fc1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.2.1 for silverstripe/silverstripe-omnipay. Confirm the publisher’s latest guidance.","source_ids":["sr-ca45c998adae865c5c7d6ffe86fe1fc1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-ca45c998adae865c5c7d6ffe86fe1fc1","url":"https://github.com/advisories/GHSA-48f2-m7jg-866x","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-48f2-m7jg-866x","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.666Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-ca45c998adae865c5c7d6ffe86fe1fc1"],"technology":"silverstripe/silverstripe-omnipay","known_exclusions":[],"conditions_summary":"### Impact\nFor 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.\n\n### Patches\nThe following versions have been patched to fix this issue:\n\n- `2.5.2`\n- `3.0.2`\n- `3.1.4`\n- `3.2.1`\n\n### Workarounds\nThere are no known workarounds for this vulnerability.\n\n### References\nN/A.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at security@silverstripe.org\n","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 2.5.2"]},{"certainty":"source_listed","source_ids":["sr-ca45c998adae865c5c7d6ffe86fe1fc1"],"technology":"silverstripe/silverstripe-omnipay","known_exclusions":[],"conditions_summary":"### Impact\nFor 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.\n\n### Patches\nThe following versions have been patched to fix this issue:\n\n- `2.5.2`\n- `3.0.2`\n- `3.1.4`\n- `3.2.1`\n\n### Workarounds\nThere are no known workarounds for this vulnerability.\n\n### References\nN/A.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at security@silverstripe.org\n","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.0.2"]},{"certainty":"source_listed","source_ids":["sr-ca45c998adae865c5c7d6ffe86fe1fc1"],"technology":"silverstripe/silverstripe-omnipay","known_exclusions":[],"conditions_summary":"### Impact\nFor 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.\n\n### Patches\nThe following versions have been patched to fix this issue:\n\n- `2.5.2`\n- `3.0.2`\n- `3.1.4`\n- `3.2.1`\n\n### Workarounds\nThere are no known workarounds for this vulnerability.\n\n### References\nN/A.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at security@silverstripe.org\n","public_affected_ranges":["ECOSYSTEM: introduced 3.1.0; fixed 3.1.4"]},{"certainty":"source_listed","source_ids":["sr-ca45c998adae865c5c7d6ffe86fe1fc1"],"technology":"silverstripe/silverstripe-omnipay","known_exclusions":[],"conditions_summary":"### Impact\nFor 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.\n\n### Patches\nThe following versions have been patched to fix this issue:\n\n- `2.5.2`\n- `3.0.2`\n- `3.1.4`\n- `3.2.1`\n\n### Workarounds\nThere are no known workarounds for this vulnerability.\n\n### References\nN/A.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at security@silverstripe.org\n","public_affected_ranges":["ECOSYSTEM: introduced 3.2.0; fixed 3.2.1"]}],"null_published_at":"2026-10-31T22:13:14.306Z","source_updated_at":"2023-11-08T04:09:12.475Z","source_disclosed_at":"2022-06-06T21:24:39.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:41:49.666Z"}],"next_cursor":null,"snapshot_revision":"42594"}