CVE-2021-41274

CVE-2021-41274 is a critical-severity cross-site request forgery (CSRF) vulnerability in solidus_auth_devise (rubygems), affecting versions >= 1.0.0, < 2.5.4. It is fixed in 2.5.4.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Authentication Bypass by CSRF Weakness

Workarounds

A couple of options:

  • If possible, change your strategy to :exception:

    class ApplicationController < ActionController::Base
  protect_from_forgery with: :exception
end

  • Add the following to config/application.rb to at least run the :exception strategy on the affected controller:

    config.after_initialize do
  Spree::UsersController.protect_from_forgery with: :exception
end

  • We've also released new Solidus versions monkey patching solidus_auth_devise with the quick fix. Those versions are v3.1.3, v.3.0.3 & v2.11.12. See GHSA-5629-8855-gf4g for details.

References

Thanks

We'd like to thank vampire000 for reporting this issue.

For more information

If you have any questions or comments about this advisory:

Impact

CSRF vulnerability that allows user account takeover.

All applications using any version of the frontend component of solidus_auth_devise are affected if protect_from_forgery method is both:

  • Executed whether as:
    • A before_action callback (the default)
    • A prepend_before_action (option prepend: true given) before the :load_object hook in Spree::UserController (most likely order to find).
  • Configured to use :null_session or :reset_session strategies (:null_session is the default in case the no strategy is given, but rails --new generated skeleton use :exception).

That means that applications that haven't been configured differently from what it's generated with Rails aren't affected.

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.

CVE-2021-41274 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.5.4); upgrading removes the vulnerable code path.

Affected versions

solidus_auth_devise (>= 1.0.0, < 2.5.4)

Security releases

solidus_auth_devise → 2.5.4 (rubygems)

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 environmentNew to Kodem? Get a demo →

Remediation advice

Users should promptly update to solidus_auth_devise version 2.5.4.

Frequently Asked Questions

  1. What is CVE-2021-41274? CVE-2021-41274 is a critical-severity cross-site request forgery (CSRF) vulnerability in solidus_auth_devise (rubygems), affecting versions >= 1.0.0, < 2.5.4. It is fixed in 2.5.4. 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 CVE-2021-41274? CVE-2021-41274 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_auth_devise are affected by CVE-2021-41274? solidus_auth_devise (rubygems) versions >= 1.0.0, < 2.5.4 is affected.
  4. Is there a fix for CVE-2021-41274? Yes. CVE-2021-41274 is fixed in 2.5.4. Upgrade to this version or later.
  5. Is CVE-2021-41274 exploitable, and should I be worried? Whether CVE-2021-41274 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 CVE-2021-41274 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 CVE-2021-41274? Upgrade solidus_auth_devise to 2.5.4 or later.

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo