Security readout for executives and security teams
Plain-English summary
Spree e-commerce sites running affected versions may let a logged-in customer access another customer’s address information through order changes. This is a privacy issue, not a system takeover. The vendor says the issue is patched in Spree 4.10.2, 5.0.7, 5.1.9, and 5.2.5.
Executive priority
Treat as a near-term privacy fix for affected Spree stores. It does not indicate full compromise, but it can expose customer address data to logged-in users. Patch during the next controlled release window, sooner for high-volume or regulated commerce environments.
Technical view
CVE-2026-22588 is an authenticated IDOR in Spree’s API order modification flow. A user modifying an order they own could cause the backend to accept address references belonging to other users and return those addresses in the response. CVSS 3.1 is 6.5, with high confidentiality impact and no integrity or availability impact listed.
Likely exposure
Exposure is limited to Spree deployments on versions before 4.10.2, 5.0.7, 5.1.9, or 5.2.5, depending on branch. The attacker needs an authenticated account. Customer address data is the primary exposed asset.
Exploitation context
The sources do not report active exploitation, and this CVE is not marked as CISA KEV in the provided bundle. Abuse requires authenticated access and interaction with order modification behavior. The issue is still business-relevant because customer address disclosure can trigger privacy, trust, and support impacts.
Researcher notes
This maps to CWE-639, authorization bypass through user-controlled keys. Focus validation on object ownership enforcement in order/address association paths. Avoid assuming broader account data exposure beyond the address information described in the advisory unless confirmed in local testing or vendor updates.
Mitigation direction
- Upgrade Spree to 4.10.2, 5.0.7, 5.1.9, or 5.2.5 as applicable.
- Prioritize internet-facing stores that allow customer account creation.
- Review vendor advisory and linked commits for branch-specific remediation details.
- If immediate upgrade is not possible, check Spree guidance for supported interim controls.
Validation and detection
- Inventory Spree versions across production, staging, and hosted storefronts.
- Confirm affected branches are not below the patched versions listed by Spree.
- Review logs for unusual authenticated order address modification activity.
- Verify API authorization checks prevent cross-user address association after patching.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-22588 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/spree/spree/security/advisories/GHSA-g268-72p7-9j6jCVE reference · x_refsource_CONFIRM
- https://github.com/spree/spree/commit/02acabdce2c5f14fd687335b068d901a957a7e72CVE reference · x_refsource_MISC
- https://github.com/spree/spree/commit/17e78a91b736b49dbea8d1bb1223c284383ee5f3CVE reference · x_refsource_MISC
- https://github.com/spree/spree/commit/b409c0fd327e7ce37f63238894670d07079eefe8CVE reference · x_refsource_MISC
- https://github.com/spree/spree/commit/d3f961c442e0015661535cbd6eb22475f76d2dc7CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.