CVE-2020-15109

Ability to change order address without triggering address validations in solidus

MEDIUM
5.3
CVSS Score
Published: August 4, 2020 at 11:00 PM UTC
Updated: June 17, 2026 at 02:56 AM UTC
2 products affected across 2 vendorsSolidusSolidus

Using solidus by solidusio?

Get instant alerts when new vulnerabilities affect solidus - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.3
Exploit prediction
EPSS 1.0%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2.8.62.10.0 ≤ v < 2.10.22.9.0 ≤ v < 2.9.6
Affected range stops below 2.10.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.8.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.9.6, so it looks safe — our inference, not a vendor statement
v < 2.10.2v < 2.8.6v < 2.9.6
Affected range stops below 2.10.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.8.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.9.6, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

5.3MEDIUMGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-20CWE-862

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card