GHSA-5629-8855-GF4G

Authentication Bypass by CSRF Weakness

Workarounds

Look at the workarounds described at GHSA-xm34-v85h-9pg2.

References

• GHSA-xm34-v85h-9pg2.

For more information

If you have any questions or comments about this advisory:

• Open an issue in solidus_auth_devise or a discussion in solidus
• Email us at [email protected]
• Contact the core team on Slack

The actual vulnerability has been discovered on solidus_auth_devise. See GHSA-xm34-v85h-9pg2 for details.

The security advisory here exists to provide an extra layer of security in the form of a monkey patch for users who don't update solidus_auth_devise. For this reason, it has been marked as low impact on this end.

A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.

GHSA-5629-8855-GF4G has a CVSS score of 9.3 (Critical). The vector is network-reachable, no privileges required, and user interaction required. 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.11.12, 3.0.3, 3.1.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

For extra security, update solidus_core to versions 3.1.3, 3.0.3 or 2.11.12.

1. What is GHSA-5629-8855-GF4G? GHSA-5629-8855-GF4G is a critical-severity cross-site request forgery (CSRF) vulnerability in solidus_core (rubygems), affecting versions < 2.11.12. It is fixed in 2.11.12, 3.0.3, 3.1.3. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
2. How severe is GHSA-5629-8855-GF4G? GHSA-5629-8855-GF4G has a CVSS score of 9.3 (Critical). 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.
3. Which versions of solidus_core are affected by GHSA-5629-8855-GF4G? solidus_core (rubygems) versions < 2.11.12 is affected.
4. Is there a fix for GHSA-5629-8855-GF4G? Yes. GHSA-5629-8855-GF4G is fixed in 2.11.12, 3.0.3, 3.1.3. Upgrade to this version or later.
5. Is GHSA-5629-8855-GF4G exploitable, and should I be worried? Whether GHSA-5629-8855-GF4G 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
6. What actually determines whether GHSA-5629-8855-GF4G 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.
7. How do I fix GHSA-5629-8855-GF4G?
   • Upgrade solidus_core to 2.11.12 or later
   • Upgrade solidus_core to 3.0.3 or later
   • Upgrade solidus_core to 3.1.3 or later

Other vulnerabilities in solidus_core