Skip to content
Fencer Intel
medium 5.3

CVE-2020-15109 json

Ability to change order address without triggering address validations in solidus

published 6y ago modified last mo. also GHSA-3mvg-rrrw-m7ph , EUVD-2020-0585

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits
0
none known

Summary

In solidus before versions 2.8.6, 2.9.6, and 2.10.2, there is an bility to change order address without triggering address validations. This vulnerability allows a malicious customer to craft request data with parameters that allow changing the address of the current order without changing the shipment costs associated with the new shipment. All stores with at least two shipping zones and different costs of shipment per zone are impacted. This problem comes from how checkout permitted attributes are structured. We have a single list of attributes that are permitted across the whole checkout, no matter the step that is being submitted. See the linked reference for more information. As a workaround, if it is not possible to upgrade to a supported patched version, please use this gist in the references section.

Patch / fix

  • rubygems solidus_frontend 2.8.6, 2.9.6, 2.10.2
  • rubygems solidus_api 2.8.6, 2.9.6, 2.10.2
  • nebulab solidus 2.8.6, 2.9.6, 2.10.2

Is CVE-2020-15109 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.00% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/solidusio/solidus/security/advisories/GHSA-3mvg-rrrw-m7ph referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
rubygems solidus_frontend
<2.8.6
>=2.9.0, <2.9.6
>=2.10.0, <2.10.2
2.8.6
2.9.6
2.10.2
rubygems solidus_api
<2.8.6
>=2.9.0, <2.9.6
>=2.10.0, <2.10.2
2.8.6
2.9.6
2.10.2

Affected products

  • solidusio solidus

Classification

Weakness

References

Sources

Fencer Intel 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.