How severe is CVE-2022-29254?

CVE-2022-29254 has a CVSS score of 3.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-29254?

CVE-2022-29254 affects the following packages: silverstripe/silverstripe-omnipay (Packagist), silverstripe/silverstripe-omnipay (Packagist), silverstripe/silverstripe-omnipay (Packagist), silverstripe/silverstripe-omnipay (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2022-29254?

Update silverstripe/silverstripe-omnipay to 2.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-29254 is resolved across your whole dependency graph.

How do I detect CVE-2022-29254 in my Packagist dependencies?

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.

How do I mitigate CVE-2022-29254 if there is no patch (or I can't update yet)?

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.

Is CVE-2022-29254 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-29254 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-29254?

CVE-2022-29254 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 52th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-29254?

CVE-2022-29254 is classified as CWE-436 (CWE-436). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-29254 published, and has it been updated?

CVE-2022-29254 was published on June 6, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

LOW severity

CVE-2022-29254 — silverstripe-omnipay

LOWFix: silverstripe/silverstripe-omnipay@7dee9a1

CVE-2022-29254 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/silverstripe-omnipay

Also known asGHSA-48f2-m7jg-866x

Published

Jun 6, 2022

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 CVE-2022-29254.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs52th percentile — riskier than 52% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

🐘silverstripe/silverstripe-omnipay🐘silverstripe/silverstripe-omnipay🐘silverstripe/silverstripe-omnipay🐘silverstripe/silverstripe-omnipay

Real-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.2
3.0.2
3.1.4
3.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

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`silverstripe/silverstripe-omnipay`	all versions	2.5.2`composer require silverstripe/silverstripe-omnipay:^2.5.2`
🐘Packagist	`silverstripe/silverstripe-omnipay`	≥ 3.0.0&&< 3.0.2	3.0.2`composer require silverstripe/silverstripe-omnipay:^3.0.2`
🐘Packagist	`silverstripe/silverstripe-omnipay`	≥ 3.1.0&&< 3.1.4	3.1.4`composer require silverstripe/silverstripe-omnipay:^3.1.4`
🐘Packagist	`silverstripe/silverstripe-omnipay`	≥ 3.2.0&&< 3.2.1	3.2.1`composer require silverstripe/silverstripe-omnipay:^3.2.1`

Affected Products

1 product · 4 configurations

Application

silverstripe-omnipaysilverstripe

≥ 3.2.0 && < 3.2.1

range

Detection & mitigation playbook

Open-source dependency

Detect
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 CVE-2022-29254 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.

Frequently Asked Questions

### 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.2` - `3.0.2` - `3.1.4` - `3.2.1` ### Workarounds T