{"answers":{"affected":"4 open source packages ship an affected version, including spree. It affects 1 product.","exploited":"There is no known exploitation of CVE-2010-3978 in the wild and no public exploit code.","fix":"Upgrade spree to a fixed version for your release line: 0.11.2 or 0.30.0.","what":"CVE-2010-3978 is a medium-severity vulnerability in n/a, published on 17 Nov 2010. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2010-3978 and fix it if it is affected.\n\nWhat it is: CVE-2010-3978 is a medium-severity vulnerability in n/a, published on 17 Nov 2010. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2010-3978 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- spree (RubyGems): affected from 0.11.0; fixed in 0.11.2\n- spree (RubyGems): affected from 0.11.0; fixed in 0.11.2\n- spree (RubyGems): affected from 0.30.0.beta1; fixed in 0.30.0\n- spree (RubyGems): affected from 0.30.0.beta1; fixed in 0.30.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2010-3978/ (Markdown: https://insights.sbomify.com/CVE-2010-3978/index.md)","id":"CVE-2010-3978","markdown":"https://insights.sbomify.com/CVE-2010-3978/index.md","name":"CVE-2010-3978","record":{"aliases":["GHSA-hwrx-wc75-mgh7"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Spree e-commerce platform","requires_auth":"high_privilege","summary":"Remote attackers can obtain sensitive information from admin JSON endpoints via JSON hijacking, requiring authenticated admin access and user interaction.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"spree","vendor":"spreecommerce"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Spree 0.11.x before 0.11.2 and 0.30.x before 0.30.0 exchanges data using JavaScript Object Notation (JSON) without a mechanism for validating requests, which allows remote attackers to obtain sensitive information via vectors involving (1) admin/products.json, (2) admin/users.json, or (3) admin/overview/get_report_data, related to a \"JSON hijacking\" issue.","ecosystems":["RubyGems"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Spree allows remote attackers to obtain sensitive information","id":"CVE-2010-3978","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"information_disclosure","year":"2010"},"n_packages":4,"n_references":8,"next":{"headline":"Information disclosure in n/a","id":"CVE-2010-3979"},"packages":[{"ecosystem":"RubyGems","fixed":["0.11.2"],"introduced":["0.11.0"],"last_affected":[],"package":"spree","purl":null,"source":"GHSA-hwrx-wc75-mgh7"},{"ecosystem":"RubyGems","fixed":["0.11.2"],"introduced":["0.11.0"],"last_affected":[],"package":"spree","purl":"pkg:gem/spree","source":"GHSA-hwrx-wc75-mgh7"},{"ecosystem":"RubyGems","fixed":["0.30.0"],"introduced":["0.30.0.beta1"],"last_affected":[],"package":"spree","purl":null,"source":"GHSA-hwrx-wc75-mgh7"},{"ecosystem":"RubyGems","fixed":["0.30.0"],"introduced":["0.30.0.beta1"],"last_affected":[],"package":"spree","purl":"pkg:gem/spree","source":"GHSA-hwrx-wc75-mgh7"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2010-3977"},"products":["n/a"],"published":"2010-11-17","related":[{"cvss_score":10,"headline":"Spreecommerce \u003c 0.60.2 Search Parameter RCE","id":"CVE-2011-10019","kev_date_added":null,"published":"2025-08-13"},{"cvss_score":9.3,"headline":"Spreecommerce \u003c 0.50.x API RCE","id":"CVE-2011-10026","kev_date_added":null,"published":"2025-08-20"},{"cvss_score":7.7,"headline":"Unauthenticated Spree Commerce users can view completed guest orders by Order ID","id":"CVE-2026-25757","kev_date_added":null,"published":"2026-02-06"},{"cvss_score":7.7,"headline":"Spree allows unauthenticated users can access all guest addresses","id":"CVE-2026-25758","kev_date_added":null,"published":"2026-02-06"},{"cvss_score":7.7,"headline":"Authorization bypass in Spree","id":"CVE-2020-26223","kev_date_added":null,"published":"2020-11-13"},{"cvss_score":7.5,"headline":"Spree API has Unauthenticated IDOR - Guest Address","id":"CVE-2026-22589","kev_date_added":null,"published":"2026-01-10"},{"cvss_score":6.5,"headline":"Spree API has Authenticated Insecure Direct Object Reference (IDOR) via Order Modification","id":"CVE-2026-22588","kev_date_added":null,"published":"2026-01-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can obtain sensitive information from admin JSON endpoints via JSON hijacking, requiring authenticated admin access and user interaction.","url":"https://insights.sbomify.com/CVE-2010-3978/"}