What is CVE-2022-29254?

CVE-2022-29254 is a low-severity security vulnerability in silverstripe/silverstripe-omnipay (composer), affecting versions < 2.5.2. It is fixed in 2.5.2, 3.0.2, 3.1.4, 3.2.1.

How severe is CVE-2022-29254?

CVE-2022-29254 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of silverstripe/silverstripe-omnipay are affected by CVE-2022-29254?

silverstripe/silverstripe-omnipay (composer) versions < 2.5.2 is affected.

Is there a fix for CVE-2022-29254?

Yes. CVE-2022-29254 is fixed in 2.5.2, 3.0.2, 3.1.4, 3.2.1. Upgrade to this version or later.

Is CVE-2022-29254 exploitable, and should I be worried?

Whether CVE-2022-29254 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-29254 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2022-29254?

Upgrade: silverstripe/silverstripe-omnipay to 2.5.2 or later, silverstripe/silverstripe-omnipay to 3.0.2 or later, silverstripe/silverstripe-omnipay to 3.1.4 or later, silverstripe/silverstripe-omnipay to 3.2.1 or later.

CVE-2022-29254 in silverstripe/silverstripe-omnipay

Q: How severe is CVE-2022-29254?

CVE-2022-29254 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of silverstripe/silverstripe-omnipay are affected by CVE-2022-29254?

silverstripe/silverstripe-omnipay (composer) versions < 2.5.2 is affected.

Q: Is there a fix for CVE-2022-29254?

Yes. CVE-2022-29254 is fixed in 2.5.2, 3.0.2, 3.1.4, 3.2.1. Upgrade to this version or later.

Q: Is CVE-2022-29254 exploitable, and should I be worried?

Whether CVE-2022-29254 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-29254 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-29254?

Upgrade: silverstripe/silverstripe-omnipay to 2.5.2 or later, silverstripe/silverstripe-omnipay to 3.0.2 or later, silverstripe/silverstripe-omnipay to 3.1.4 or later, silverstripe/silverstripe-omnipay to 3.2.1 or later.

Summary

Failed payment recorded has completed in Silverstripe Omnipay

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]

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.

CVE-2022-29254 has a CVSS score of 3.7 (Low). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.5.2, 3.0.2, 3.1.4, 3.2.1); upgrading removes the vulnerable code path.

Affected versions

silverstripe/silverstripe-omnipay (< 2.5.2) silverstripe/silverstripe-omnipay (>= 3.0.0, < 3.0.2) silverstripe/silverstripe-omnipay (>= 3.1.0, < 3.1.4) silverstripe/silverstripe-omnipay (>= 3.2.0, < 3.2.1)

Security releases

silverstripe/silverstripe-omnipay → 2.5.2 (composer) silverstripe/silverstripe-omnipay → 3.0.2 (composer) silverstripe/silverstripe-omnipay → 3.1.4 (composer) silverstripe/silverstripe-omnipay → 3.2.1 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The following versions have been patched to fix this issue:

2.5.2
3.0.2
3.1.4
3.2.1

Frequently Asked Questions

What is CVE-2022-29254? CVE-2022-29254 is a low-severity security vulnerability in silverstripe/silverstripe-omnipay (composer), affecting versions < 2.5.2. It is fixed in 2.5.2, 3.0.2, 3.1.4, 3.2.1.
How severe is CVE-2022-29254? CVE-2022-29254 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of silverstripe/silverstripe-omnipay are affected by CVE-2022-29254? silverstripe/silverstripe-omnipay (composer) versions < 2.5.2 is affected.
Is there a fix for CVE-2022-29254? Yes. CVE-2022-29254 is fixed in 2.5.2, 3.0.2, 3.1.4, 3.2.1. Upgrade to this version or later.
Is CVE-2022-29254 exploitable, and should I be worried? Whether CVE-2022-29254 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-29254 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-29254?
- Upgrade silverstripe/silverstripe-omnipay to 2.5.2 or later
- Upgrade silverstripe/silverstripe-omnipay to 3.0.2 or later
- Upgrade silverstripe/silverstripe-omnipay to 3.1.4 or later
- Upgrade silverstripe/silverstripe-omnipay to 3.2.1 or later