CVE-2008-7310 json
Spree does not properly restrict the use of a hash to provide values for a model's attributes
published 2012-04-04 14 y ago modified 2026-06-16 4 mo ago also GHSA-7h48-m3rw-vr27 , EUVD-2022-3007
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 69%
- public exploits
- 0
- none known
Summary
Spree 0.2.0 does not properly restrict the use of a hash to provide values for a model's attributes, which allows remote attackers to set the Order state value and bypass the intended payment step via a modified URL, related to a "mass assignment" vulnerability.
Patch / fix
- rubygems spree 0.4.0
Exploit prediction
1.23% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | spree | <0.4.0 |
0.4.0 |
Classification
- Weakness
-
- CWE-255 Credentials Management Errors
References
-
spreecommerce.com
/blog/2008/09/16/security-vulnerability-mass-assignment-of-order-params/
vendor-advisory
-
railspikes.com
/2008/9/22/is-your-rails-application-safe-from-mass-assignment
web
-
nvd.nist.gov
/vuln/detail/CVE-2008-7310
advisory
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/spree/CVE-2008-7310.yml
web
-
github.com
/spree/spree
package
-
spreecommerce.com
/blog/security-vulnerability-mass-assignment
web
-
web.archive.org
/web/20080925003904/http://railspikes.com/2008/9/22/is-your-rails-application-safe-from-mass-assignment
web
-
web.archive.org
/web/20101128024717/http://spreecommerce.com/blog/2008/09/16/security-vulnerability-mass-assignment-of-order-p
web
-
spreecommerce.com
/blog/2008/09/16/security-vulnerability-mass-assignment-of-order-params
web
Sources
- CVE List CVE-2008-7310
- GitHub Advisory GHSA-7h48-m3rw-vr27
- NVD CVE-2008-7310
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.