GHSA-48f2-m7jg-866x is a low-severity (CVSS 3.7) CWE-436 vulnerability in silverstripe/silverstripe-omnipay. A fix is available for silverstripe/silverstripe-omnipay — see the affected versions and patch details below.
Failed payment recorded has completed in Silverstripe Omnipay
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-48f2-m7jg-866x.
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.
How urgent is this, really
GHSA-48f2-m7jg-866x plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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.2composer require silverstripe/silverstripe-omnipay:^2.5.2 |
| 🐘Packagist | silverstripe/silverstripe-omnipay | ≥ 3.0.0&&< 3.0.2 | 3.0.2composer require silverstripe/silverstripe-omnipay:^3.0.2 |
| 🐘Packagist | silverstripe/silverstripe-omnipay | ≥ 3.1.0&&< 3.1.4 | 3.1.4composer require silverstripe/silverstripe-omnipay:^3.1.4 |
| 🐘Packagist | silverstripe/silverstripe-omnipay | ≥ 3.2.0&&< 3.2.1 | 3.2.1composer require silverstripe/silverstripe-omnipay:^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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-48f2-m7jg-866x can be triaged on real exposure rather than presence alone.
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 Security finds GHSA-48f2-m7jg-866x across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.