BlackTreeCVE Intelligencespree · spree
Official source article: GitHub GHSA-87FH-RC96-6FR6 ↗. Check the applicable product and release in the original source.
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| RubyGemsspree_api | ECOSYSTEM: introduced 0; fixed 4.10.3 | 4.10.3 | OSV record ↗aggregator derived · 22 Feb 2026 |
| RubyGemsspree_api | ECOSYSTEM: introduced 5.0.0; fixed 5.0.8 | 5.0.8 | OSV record ↗aggregator derived · 22 Feb 2026 |
| RubyGemsspree_api | ECOSYSTEM: introduced 5.1.0; fixed 5.1.10 | 5.1.10 | OSV record ↗aggregator derived · 22 Feb 2026 |
| RubyGemsspree_api | ECOSYSTEM: introduced 5.2.0; fixed 5.2.7 | 5.2.7 | OSV record ↗aggregator derived · 22 Feb 2026 |
| RubyGemsspree_api | ECOSYSTEM: introduced 5.3.0; fixed 5.3.2 | 5.3.2 | OSV record ↗aggregator derived · 22 Feb 2026 |
| rubygemsspree_api | < 4.10.3 | 4.10.3 | GitHub advisory ↗upstream repository advisory · 13 Feb 2026 |
| rubygemsspree_api | >= 5.0.0, < 5.0.8 | 5.0.8 | GitHub advisory ↗upstream repository advisory · 13 Feb 2026 |
| rubygemsspree_api | >= 5.1.0, < 5.1.10 | 5.1.10 | GitHub advisory ↗upstream repository advisory · 13 Feb 2026 |
| rubygemsspree_api | >= 5.2.0, < 5.2.7 | 5.2.7 | GitHub advisory ↗upstream repository advisory · 13 Feb 2026 |
| rubygemsspree_api | >= 5.3.0, < 5.3.2 | 5.3.2 | GitHub advisory ↗upstream repository advisory · 13 Feb 2026 |
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Patch availableSpree is an open source e-commerce solution built with Ruby on Rails. A critical IDOR vulnerability exists in Spree Commerce's guest checkout flow that allows any guest user to bind arbitrary guest addresses to their order by manipulating address ID parameters. This enables unauthorized access to other guests' personally identifiable information (PII) including names, addresses and phone numbers. The vulnerability bypasses existing ownership validation checks and affects all guest checkout transactions. This vulnerability is fixed in 4.10.3, 5.0.8, 5.1.10, 5.2.7, and 5.3.2.
Spree is an open source e-commerce solution built with Ruby on Rails. A critical IDOR vulnerability exists in Spree Commerce's guest checkout flow that allows any guest user to bind arbitrary guest addresses to their order by manipulating address ID parameters. This enables unauthorized access to other guests' personally identifiable information (PII) including names, addresses and phone numbers. The vulnerability bypasses existing ownership validation checks and affects all guest checkout transactions. This vulnerability is fixed in 4.10.3, 5.0.8, 5.1.10, 5.2.7, and 5.3.2.
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
Spree is an open source e-commerce solution built with Ruby on Rails. A critical IDOR vulnerability exists in Spree Commerce's guest checkout flow that allows any guest user to bind arbitrary guest addresses to their order by manipulating address ID parameters. This enables unauthorized access to other guests' personally identifiable information (PII) including names, addresses and phone numbers. The vulnerability bypasses existing ownership validation checks and affects all guest checkout transactions. This vulnerability is fixed in 4.10.3, 5.0.8, 5.1.10, 5.2.7, and 5.3.2.
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.
CWE-639: Authorization Bypass Through User-Controlled Key. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:PCommon Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 6 Feb 2026 · Last source change 9 Feb 2026, 15:26 UTC · CWE-639 · Authorization Bypass Through User-Controlled Key
Core structured fields are present and their contributing authorities are shown above.
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.