How severe is GHSA-3ghg-3787-w2xr?

GHSA-3ghg-3787-w2xr has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-3ghg-3787-w2xr?

GHSA-3ghg-3787-w2xr affects the following packages: spree_core (RubyGems), spree_core (RubyGems), spree_core (RubyGems), spree_core (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-3ghg-3787-w2xr?

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.

How do I detect GHSA-3ghg-3787-w2xr in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for spree_core. 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.

How do I mitigate GHSA-3ghg-3787-w2xr if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-3ghg-3787-w2xr?

O3 pinpoints whether GHSA-3ghg-3787-w2xr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-3ghg-3787-w2xr actively exploited in the wild?

No public exploit code has been indexed for GHSA-3ghg-3787-w2xr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-3ghg-3787-w2xr?

GHSA-3ghg-3787-w2xr has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 30th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-3ghg-3787-w2xr published, and has it been updated?

GHSA-3ghg-3787-w2xr was published on January 8, 2026 and was last updated on February 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎 RubyGems

GHSA-3ghg-3787-w2xr

HIGH

Spree API has Unauthenticated IDOR - Guest Address

Also known asCVE-2026-22589

Published

Jan 8, 2026

Updated

Feb 3, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk30th percentile+0.29%

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.

Blast Radius

4 pkgs affected

💎spree_core💎spree_core💎spree_core💎spree_core

Real-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

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`spree_core`	≥ 4.0.0&&< 4.10.2	4.10.2
💎RubyGems	`spree_core`	≥ 5.0.0&&< 5.0.7	5.0.7
💎RubyGems	`spree_core`	≥ 5.1.0&&< 5.1.9	5.1.9
💎RubyGems	`spree_core`	≥ 5.2.0&&< 5.2.5	5.2.5

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for spree_core. 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_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 pinpoints whether GHSA-3ghg-3787-w2xr 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-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

### 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) * A

O3 Security · Impact-Aware SCA

Is GHSA-3ghg-3787-w2xr in your dependencies?

O3 detects GHSA-3ghg-3787-w2xr across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works