GHSA-m2jr-hmc3-qmpr
HIGHGHSA-m2jr-hmc3-qmpr is a high-severity (CVSS 7.7) CWE-863 vulnerability in spree_api. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-m2jr-hmc3-qmpr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Authorization bypass in Spree
Blast Radius
spree_api💎spree_api💎spree_apiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.
Description
Impact
The perpetrator could query the API v2 Order Status endpoint with an empty string passed as an Order token
Patches
Please upgrade to 3.7.11, 4.0.4, or 4.1.11 depending on your used Spree version. Users of Spree < 3.7 are not affected.
References
Pull request with a fix and in-depth explanation - https://github.com/spree/spree/pull/10573
For more information
If you have any questions or comments about this advisory:
- Email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | spree_api | ≥ 3.7.0&&< 3.7.13 | 3.7.13 |
| 💎RubyGems | spree_api | ≥ 4.0.0&&< 4.0.5 | 4.0.5 |
| 💎RubyGems | spree_api | ≥ 4.1.0&&< 4.1.12 | 4.1.12 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for spree_api. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update spree_api to 3.7.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m2jr-hmc3-qmpr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-m2jr-hmc3-qmpr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-m2jr-hmc3-qmpr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-m2jr-hmc3-qmpr in your dependencies?
O3 detects GHSA-m2jr-hmc3-qmpr across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.