GHSA-3ghg-3787-w2xr is a high-severity (CVSS 7.5) CWE-639 vulnerability in spree_core. A fix is available for spree_core — see the affected versions and patch details below.
Spree API has Unauthenticated IDOR - Guest Address
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for GHSA-3ghg-3787-w2xr.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-3ghg-3787-w2xr plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
spree_core💎spree_core💎spree_core💎spree_coreReal-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
Summary
An Unauthenticated Insecure Direct Object Reference (IDOR) vulnerability was identified that allows an unauthenticated attacker to access guest address information without supplying valid credentials or session cookies.
Details
During testing, it was observed that all guest users can make an unauthenticated request to retrieve address data belonging to other guest users by manipulating object identifiers. The attacker would need to know the storefront URL structure to perform this attack (which can be learnt after creating a registered user account).
Affected Component(s)
- Address Edit endpoint:
/addresses/{addressId}/edit
Root Cause
- Faulty authorization check in CanCanCan Ability class:
- can :manage, ::Spree::Address, user_id: user.id
+ can :manage, ::Spree::Address, user_id: user.id if user.persisted?
the user object in Spree::Ability class for guest users is a Spree.user_class.new object.
Addresses endpoint to access it is part of the spree_storefront gem. Headless builds using APIs are not affected, as the Addresses endpoint there is only for registered users, and records are scoped to the currently signed-in user.
PoC
Preconditions
- No authentication required
- No cookies or session tokens set
To reproduce this vulnerability simply perform the request shown below, replacing the number with an arbitrary value.
For the initial request the Guest Address id = 6 is used to obtain the information
Request
GET /addresses/6/edit
Repeat the request and check the response, in this example using Guest Address id = 2.
Request
GET /addresses/2/edit
Impact
An unauthenticated attacker can:
- Enumerate and retrieve guest address information (Addresses associated with User accounts are NOT affected)
- Access personally identifiable information (PII) such as:
- Full names
- Physical addresses
- Phone numbers (if present)
This vulnerability could lead to:
- Privacy violations
- Regulatory compliance issues (e.g., GDPR)
- Loss of user trust
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | spree_core | ≥ 4.0.0&&< 4.10.2 | 4.10.2bundle update spree_core --conservative |
| 💎RubyGems | spree_core | ≥ 5.0.0&&< 5.0.7 | 5.0.7bundle update spree_core --conservative |
| 💎RubyGems | spree_core | ≥ 5.1.0&&< 5.1.9 | 5.1.9bundle update spree_core --conservative |
| 💎RubyGems | spree_core | ≥ 5.2.0&&< 5.2.5 | 5.2.5bundle update spree_core --conservative |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for spree_core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update spree_core to 4.10.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3ghg-3787-w2xr 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3ghg-3787-w2xr can be triaged on real exposure rather than presence alone.
Tailored to GHSA-3ghg-3787-w2xr. 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-3ghg-3787-w2xr in your dependencies?
O3 Security finds GHSA-3ghg-3787-w2xr across RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.