Advisory record · GHSA-3mvg-rrrw-m7ph

Ability to change order address without triggering address validations in solidus

CVSS 5.3 MediumEPSS 0.0100 · 63rd percentile

Published by the GitHub Advisory Database at 4 Aug 2020, 22:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
solidus_frontendRubyGems<2.8.6 || >=2.9.0, <2.9.6 || >=2.10.0, <2.10.22.8.6, 2.9.6, 2.10.2
solidus_apiRubyGems<2.8.6 || >=2.9.0, <2.9.6 || >=2.10.0, <2.10.22.8.6, 2.9.6, 2.10.2
Identifiers
GHSA-3mvg-rrrw-m7ph · CVE-2020-15109
Weakness (CWE)
CWE-20 · CWE-862
Published
4 Aug 2020
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Solidus_frontend and solidus_api, versions before 2.8.6, from 2.9.0 before 2.9.6, and from 2.10.0 before 2.10.2, allow a customer to submit crafted checkout requests that change the order's shipping address without the shipping costs being recalculated for the new zone. Any authenticated customer who can reach checkout can exploit this to pay a lower shipping rate, or to move to an address in a zone the store meant to exclude. Upgrade solidus_frontend and solidus_api to 2.8.6, 2.9.6, or 2.10.2, depending on the release line in use.

Written 8 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0100, the 63rd percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:16 UTC First seen by agentprime
  2. 31 Oct 2026, 15:16 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.