solidus_auth_devise

Version	Released
`2.6.0` minor	Apr 08, 2026
`2.5.9` patch	Jan 30, 2024
`2.5.8` patch	May 04, 2023
`2.5.7` patch	Oct 31, 2022
`2.5.6` patch	Sep 30, 2022
`2.5.5` patch	Sep 19, 2022
`2.5.4` patch	Nov 17, 2021
`2.5.3` patch 1 CVE	Jan 29, 2021
`2.5.2` patch 1 CVE	Nov 11, 2020
`2.5.1` patch 1 CVE	Oct 23, 2020
`2.5.0` minor 1 CVE	Oct 07, 2020
`2.4.0` minor 1 CVE	Nov 18, 2019
`2.3.0` minor 1 CVE	Aug 19, 2019
`2.2.0` minor 1 CVE	Jun 13, 2019
`2.1.0` minor 1 CVE	Jan 22, 2018
`2.0.0` major 1 CVE	Sep 20, 2017
`1.6.4` patch 1 CVE	Jul 24, 2017
`1.6.3` patch 1 CVE	May 09, 2017
`1.6.2` patch 1 CVE	Nov 18, 2016
`1.6.1` patch 1 CVE	Aug 24, 2016
`1.6.0` minor 1 CVE	Aug 23, 2016
`1.5.0` minor 1 CVE	Jul 18, 2016
`1.4.0` minor 1 CVE	May 16, 2016
`1.3.0` minor 1 CVE	Jan 12, 2016
`1.2.3` patch 1 CVE	Nov 30, 2015
`1.2.2` patch 1 CVE	Oct 01, 2015
`1.2.1` patch 1 CVE	Aug 13, 2015
`1.2.0` minor 1 CVE	Jul 22, 2015
`1.1.0` minor 1 CVE	Jun 03, 2015
`1.0.0` initial 1 CVE	May 26, 2015

2.6.0 minor

Apr 08, 2026

2.5.9 patch

Jan 30, 2024

2.5.8 patch

May 04, 2023

2.5.7 patch

Oct 31, 2022

2.5.6 patch

Sep 30, 2022

2.5.5 patch

Sep 19, 2022

2.5.4 patch

Nov 17, 2021

2.5.3 patch

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

Jan 29, 2021

2.5.2 patch

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

Nov 11, 2020

2.5.1 patch

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

Oct 23, 2020

2.5.0 minor

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

Oct 07, 2020

2.4.0 minor

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

Nov 18, 2019

2.3.0 minor

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

Aug 19, 2019

2.2.0 minor

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

Jun 13, 2019

2.1.0 minor

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

Jan 22, 2018

2.0.0 major

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

Sep 20, 2017

1.6.4 patch

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

Jul 24, 2017

1.6.3 patch

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

May 09, 2017

1.6.2 patch

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

Nov 18, 2016

1.6.1 patch

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

Aug 24, 2016

1.6.0 minor

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

Aug 23, 2016

1.5.0 minor

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

Jul 18, 2016

1.4.0 minor

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

May 16, 2016

1.3.0 minor

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

Jan 12, 2016

1.2.3 patch

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

Nov 30, 2015

1.2.2 patch

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

Oct 01, 2015

1.2.1 patch

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

Aug 13, 2015

1.2.0 minor

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

Jul 22, 2015

1.1.0 minor

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

Jun 03, 2015

1.0.0 initial

1 CVE

CVE-2021-41274 GHSA-xm34-v85h-9pg2 Nov 18, 2021

Authentication Bypass by CSRF Weakness

9.3 / 10

Critical

Network Low None Required Changed High High None

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.

Patches

Users should promptly update to solidus_auth_devise version 2.5.4.

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:

Open an issue in solidus_auth_devise or a discussion in solidus
Email us at security@solidus.io
Contact the core team on Slack

Affected versions


          1.0.0


          1.1.0


          1.2.0


          1.2.1


          1.2.2


          1.2.3


          1.3.0


          1.4.0


          1.5.0


          1.6.0


          1.6.1


          1.6.2

+ 11 more


            1.6.3


            1.6.4


            2.0.0


            2.1.0


            2.2.0


            2.3.0


            2.4.0


            2.5.0


            2.5.1


            2.5.2


            2.5.3

Fixed in


          2.5.4

References

Updated Jul 08, 2026 · Source: OSV.dev

May 26, 2015

Activity

Reach

Details