CVE-2023-32065 — oro/commerce
MEDIUMCVE-2023-32065 is a medium-severity (CVSS 5.8) CWE-284 vulnerability in oro/commerce. A fix is available for oro/commerce — see the affected versions and patch details below.
OroCommerce get-totals-for-checkout API endpoint returns unwanted data
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2023-32065 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
oro/commerce🐘oro/commerce🐘oro/commerceReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
OroCommerce is an open-source Business to Business Commerce application built with flexibility in mind. Detailed Order totals information may be received by Order ID. This issue is patched in version 5.0.11 and 5.1.1.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | oro/commerce | ≥ 4.2.0 | No fix |
| 🐘Packagist | oro/commerce | ≥ 5.0.0&&< 5.0.11 | 5.0.11composer require oro/commerce:^5.0.11 |
| 🐘Packagist | oro/commerce | ≥ 5.1.0&&< 5.1.1 | 5.1.1composer require oro/commerce:^5.1.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for oro/commerce, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of oro/commerce has shipped for CVE-2023-32065 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2023-32065 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2023-32065. 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-2023-32065 in your dependencies?
O3 Security finds CVE-2023-32065 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.