CVE-2020-15269

Workarounds

In your project directory create a decorator file app/controllers/spree/api/v2/base_controller_decotatror.rb with contents:

module Spree
  module Api
    module V2
      module BaseControllerDecorator
        private

        def spree_current_user
          return nil unless doorkeeper_token
          return @spree_current_user if @spree_current_user

          doorkeeper_authorize!

          @spree_current_user ||= ::Spree.user_class.find_by(id: doorkeeper_token.resource_owner_id)
        end
     end
  end
end

Spree::Api::V2::BaseController.prepend(Spree::Api::V2::BaseControllerDecorator)

For more information

If you have any questions or comments about this advisory:

• Email us at [email protected]

The perpetrator who previously obtained an old expired user token could use it to access Storefront API v2 endpoints.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2020-15269 has a CVSS score of 7.4 (High). 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 (3.7.11, 4.0.4, 4.1.11); upgrading removes the vulnerable code path.

Kodem intelligence

Please upgrade to 3.7.11, 4.0.4, or 4.1.11 depending on your used Spree version.

1. What is CVE-2020-15269? CVE-2020-15269 is a high-severity improper authentication vulnerability in spree (rubygems), affecting versions < 3.7.11. It is fixed in 3.7.11, 4.0.4, 4.1.11. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2020-15269? CVE-2020-15269 has a CVSS score of 7.4 (High). 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 spree are affected by CVE-2020-15269? spree (rubygems) versions < 3.7.11 is affected.
4. Is there a fix for CVE-2020-15269? Yes. CVE-2020-15269 is fixed in 3.7.11, 4.0.4, 4.1.11. Upgrade to this version or later.
5. Is CVE-2020-15269 exploitable, and should I be worried? Whether CVE-2020-15269 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-2020-15269 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-2020-15269?
   • Upgrade spree to 3.7.11 or later
   • Upgrade spree to 4.0.4 or later
   • Upgrade spree to 4.1.11 or later