What is CVE-2020-11007?

CVE-2020-11007 is a critical-severity improper input validation vulnerability in com.shopizer:sm-core-model (maven), affecting versions < 2.11.0. It is fixed in 2.11.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.

How severe is CVE-2020-11007?

CVE-2020-11007 has a CVSS score of 6.5 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of com.shopizer:sm-core-model are affected by CVE-2020-11007?

com.shopizer:sm-core-model (maven) versions < 2.11.0 is affected.

Is there a fix for CVE-2020-11007?

Yes. CVE-2020-11007 is fixed in 2.11.0. Upgrade to this version or later.

Is CVE-2020-11007 exploitable, and should I be worried?

Whether CVE-2020-11007 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2020-11007 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2020-11007?

Upgrade com.shopizer:sm-core-model to 2.11.0 or later.

CVE-2020-11007 in com.shopizer:sm-core-model

Q: How severe is CVE-2020-11007?

CVE-2020-11007 has a CVSS score of 6.5 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of com.shopizer:sm-core-model are affected by CVE-2020-11007?

com.shopizer:sm-core-model (maven) versions < 2.11.0 is affected.

Q: Is there a fix for CVE-2020-11007?

Yes. CVE-2020-11007 is fixed in 2.11.0. Upgrade to this version or later.

Q: Is CVE-2020-11007 exploitable, and should I be worried?

Whether CVE-2020-11007 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2020-11007 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2020-11007?

Upgrade com.shopizer:sm-core-model to 2.11.0 or later.

Summary

Negative charge in shopping cart in Shopizer

Workarounds

Without uprading, it's possible to just apply the fixes in the same files it's done for the patch. Or you use javax constraint validation on the quantity parameter.

References

Input Validation
Using bean validation constraint
Commits with fixes
CVE Details below :
Mitre
NVD

Credits

Found and solved by Yannick Gosset from Aix-Marseille University cybersecurity
master program supervised by Yassine Ilmi

Impact

Using API or Controller based versions negative quantity is not adequately validated hence creating incorrect shopping cart and order total.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2020-11007 has a CVSS score of 6.5 (Critical). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.11.0); upgrading removes the vulnerable code path.

Affected versions

com.shopizer:sm-core-model (< 2.11.0)

Security releases

com.shopizer:sm-core-model → 2.11.0 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Adding a back-end verification to check that quantity parameter isn't negative. If so, it is set to 1. Patched in 2.11.0

Frequently Asked Questions

What is CVE-2020-11007? CVE-2020-11007 is a critical-severity improper input validation vulnerability in com.shopizer:sm-core-model (maven), affecting versions < 2.11.0. It is fixed in 2.11.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
How severe is CVE-2020-11007? CVE-2020-11007 has a CVSS score of 6.5 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of com.shopizer:sm-core-model are affected by CVE-2020-11007? com.shopizer:sm-core-model (maven) versions < 2.11.0 is affected.
Is there a fix for CVE-2020-11007? Yes. CVE-2020-11007 is fixed in 2.11.0. Upgrade to this version or later.
Is CVE-2020-11007 exploitable, and should I be worried? Whether CVE-2020-11007 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2020-11007 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2020-11007? Upgrade com.shopizer:sm-core-model to 2.11.0 or later.