GHSA-w8rc-pgxq-x2cj is a medium-severity (CVSS 6.5) Improper Input Validation vulnerability in com.shopizer:sm-core-model. O3 Security confirms whether GHSA-w8rc-pgxq-x2cj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Negative charge in shopping cart in Shopizer
Real-World Exposure
com.shopizer:sm-core-modelReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Using API or Controller based versions negative quantity is not adequately validated hence creating incorrect shopping cart and order total.
Patches
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
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.shopizer:sm-core-model | all versions | 2.11.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.shopizer:sm-core-model. 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 com.shopizer:sm-core-model to 2.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w8rc-pgxq-x2cj 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 GHSA-w8rc-pgxq-x2cj 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 GHSA-w8rc-pgxq-x2cj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-w8rc-pgxq-x2cj in your dependencies?
O3 detects GHSA-w8rc-pgxq-x2cj across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.