CVE-2020-15109
MEDIUMCVE-2020-15109 is a medium-severity (CVSS 5.3) Improper Input Validation vulnerability in solidus_frontend. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2020-15109 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Ability to change order address without triggering address validations in solidus
Real-World Exposure
solidus_frontend💎solidus_frontend💎solidus_frontend💎solidus_api💎solidus_api💎solidus_apiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.
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 Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | solidus_frontend | all versions | 2.8.6 |
| 💎RubyGems | solidus_frontend | ≥ 2.9.0&&< 2.9.6 | 2.9.6 |
| 💎RubyGems | solidus_frontend | ≥ 2.10.0&&< 2.10.2 | 2.10.2 |
| 💎RubyGems | solidus_api | all versions | 2.8.6 |
| 💎RubyGems | solidus_api | ≥ 2.9.0&&< 2.9.6 | 2.9.6 |
| 💎RubyGems | solidus_api | ≥ 2.10.0&&< 2.10.2 | 2.10.2 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for solidus_frontend. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update solidus_frontend to 2.8.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-15109 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2020-15109 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2020-15109. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2020-15109 in your dependencies?
O3 detects CVE-2020-15109 across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.