Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3

Ability to change order address without triggering address validations in solidus

CVE-2020-15109GHSA-3mvg-rrrw-m7ph

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (solidus_frontend 2.10.2, 2.9.6, 2.8.6; solidus_api 2.10.2, 2.9.6, 2.8.6), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • RubyGems solidus_frontend

    Affected
    < 2.8.6>= 2.9.0, < 2.9.6>= 2.10.0, < 2.10.2
    Fixed in
    2.8.6, 2.10.2, 2.9.6

  • RubyGems solidus_api

    Affected
    < 2.8.6>= 2.9.0, < 2.9.6>= 2.10.0, < 2.10.2
    Fixed in
    2.8.6, 2.10.2, 2.9.6

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS
  • CVE-2020-15109: 1.00% estimated exploitation activity in the next 30 days; percentile 62.82 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact 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. E.g. 1. Store admin configured the store so that there are two zones in US: - East Cost Zone - Shipping Method cost: $1 - West Cost Zone - Shipping Method cost: $10 The attacker user can know that shipping to NY is less expensive than to LA just by testing different addresses in checkout. 2. The attacker user enters any NY shipping address in the address step 3. The attacker user chooses the $1 delivery option 4. The attacker user crafts a request with their real LA address, similar to: 5. The attacker user proceeds with checking out with a new address and the $1 shipment costs. Another scenario where this could be dangerous is: You cannot ship products in some zones and you…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-3mvg-rrrw-m7ph

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-15109

Advisory: Ability to change order address without triggering address validations in solidus
IDs: CVE-2020-15109, GHSA-3mvg-rrrw-m7ph
Record: https://patchnext.com/advisories/cve-2020-15109 (revision 1, source checked 26 Oct 2026, 15:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: solidus_frontend 2.10.2, 2.9.6, 2.8.6; solidus_api 2.10.2, 2.9.6, 2.8.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- RubyGems solidus_frontend: affected < 2.8.6; >= 2.9.0, < 2.9.6; >= 2.10.0, < 2.10.2; fixed in 2.8.6, 2.10.2, 2.9.6
- RubyGems solidus_api: affected < 2.8.6; >= 2.9.0, < 2.9.6; >= 2.10.0, < 2.10.2; fixed in 2.8.6, 2.10.2, 2.9.6

## Suggested inspection (read-only)
- RubyGems solidus_frontend: check the installed version with your package manager.
- RubyGems solidus_api: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on solidus_frontend, solidus_api.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3mvg-rrrw-m7ph (GitHub-reviewed advisory GHSA-3mvg-rrrw-m7ph lists affected ranges: RubyGems solidus_frontend >=0 =2.9.0 =2.10.0 =0 =2.9.0 =2.10.0 <2.10.2)

Commands are suggestions: review each one before running it.

Loading voting…