GHSA-48f2-m7jg-866x
LOWFailed payment recorded has completed in Silverstripe Omnipay
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
silverstripe/silverstripe-omnipay🐘silverstripe/silverstripe-omnipay🐘silverstripe/silverstripe-omnipay🐘silverstripe/silverstripe-omnipayReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Impact
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.
Patches
The following versions have been patched to fix this issue:
2.5.23.0.23.1.43.2.1
Workarounds
There are no known workarounds for this vulnerability.
References
N/A.
For more information
If you have any questions or comments about this advisory:
- Email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | silverstripe/silverstripe-omnipay | all versions | 2.5.2 |
| 🐘Packagist | silverstripe/silverstripe-omnipay | ≥ 3.0.0&&< 3.0.2 | 3.0.2 |
| 🐘Packagist | silverstripe/silverstripe-omnipay | ≥ 3.1.0&&< 3.1.4 | 3.1.4 |
| 🐘Packagist | silverstripe/silverstripe-omnipay | ≥ 3.2.0&&< 3.2.1 | 3.2.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/silverstripe-omnipay. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update silverstripe/silverstripe-omnipay to 2.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-48f2-m7jg-866x is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-48f2-m7jg-866x is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-48f2-m7jg-866x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-48f2-m7jg-866x in your dependencies?
O3 detects GHSA-48f2-m7jg-866x across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.