Loading...
Skip to main content

CVE-2020-15269 — Vulnerability in spree — CVE Details

HIGH

Ensure that doorkeeper_token is valid when authenticating requests in API v2 calls

Published October 20, 2020Updated July 8, 2026Source: osv

Summary

### Impact The perpetrator who previously obtained an old expired user token could use it to access Storefront API v2 endpoints. ### Patches Please upgrade to 3.7.11, 4.0.4, or 4.1.11 depending on your used Spree version. ### Workarounds In your project directory create a decorator file `app/controllers/spree/api/v2/base_controller_decotatror.rb` with contents: ```ruby 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 [security@spreecommerce.org](mailto:security@spreecommerce.org)

Advisory Timeline

  • First published October 20, 2020 (2183 days ago).
  • Last revised July 8, 2026 — 2086 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Bundler
Update spree to 3.7.11 or later
gem install spree -v 3.7.11
Bundler
Update spree to 4.1.11 or later
gem install spree -v 4.1.11
Bundler
Update spree to 4.0.4 or later
gem install spree -v 4.0.4

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (3)

Affects 1 ecosystem: rubygems (1).

PackageEcosystemAffectedFixed In
spree
rubygems
0.0.5, 0.0.6, 0.0.7, 0.0.8 (+259 more)3.7.11
spree
rubygems
4.1.0, 4.1.1, 4.1.10, 4.1.2 (+7 more)4.1.11
spree
rubygems
4.0.0, 4.0.1, 4.0.2, 4.0.34.0.4

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 7.4 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Frequently Asked Questions

What is CVE-2020-15269?
Ensure that doorkeeper_token is valid when authenticating requests in API v2 calls This vulnerability has been assigned a severity rating of HIGH (CVSS score: 7.4/10).
How do I check if my project is affected by CVE-2020-15269?
CVE-2020-15269 affects spree. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2020-15269 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
7.4

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

GHSA-f8cm-364f-q9qh

Related CVEs

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies