CVE-2020-11007: Negative charge in shopping cart in Shopizer

com.shopizer:sm-core-model Updated 02 Oct 2025

Summary

22/04/2020
Yes i
Critical
6.5

CVE-2020-11007: Negative charge in shopping cart in Shopizer. Affects com.shopizer:sm-core-model versions < 2.11.0. Fixed in 2.11.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Shopizer is an open-source e-commerce platform written in Java. It provides a range of features for building and managing online stores. The 'com.shopizer:sm-core-model' package is a core component of Shopizer, responsible for handling shopping cart functionality and order processing.

Vulnerability Detail

The vulnerability (CVE-2020-11007) in Shopizer allows for the creation of incorrect shopping carts and order totals due to inadequate validation of negative quantity inputs. This vulnerability can be exploited through the API or Controller based versions of Shopizer. An attacker can manipulate the quantity parameter to set a negative value, resulting in incorrect calculations and potentially leading to financial loss for the affected online store.

How To Fix

Latest published version: 3.2.3 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.11.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If upgrading to the latest version is not feasible, a temporary workaround is to manually apply the fixes made in the relevant files. Alternatively, the javax constraint validation can be used on the quantity parameter to ensure it is not negative.

Conclusion

The vulnerability in Shopizer (CVE-2020-11007) allows for the creation of incorrect shopping carts and order totals due to inadequate validation of negative quantity inputs. To mitigate this vulnerability, it is recommended to upgrade to Shopizer version 2.11.0 or later. If upgrading is not possible, manual fixes or the use of javax constraint validation can be employed. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for com.shopizer:sm-core-model →

Share this vulnerability

FAQ

The vulnerability allows for the creation of incorrect shopping carts and order totals, potentially leading to financial loss for the affected online store.

To fix this vulnerability, upgrade to Shopizer version 2.11.0 or later. Alternatively, manually apply the fixes made in the relevant files or use javax constraint validation on the quantity parameter.

Yes, if upgrading is not possible, you can apply the fixes manually or use javax constraint validation on the quantity parameter.

Yes, you can refer to the OWASP Input Validation Cheat Sheet and the Java EE tutorial on bean validation. Additionally, the GitHub commits with the fixes provide more technical details.

The vulnerability was found and solved by Yannick Gosset from Aix-Marseille University cybersecurity master program, under the supervision of Yassine Ilmi.

How To Fix

Latest published version: 3.2.3 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.11.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback