Composer oro/commerce has 4 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.
| CVE | Title | Severity | CVSS | Affected | Fixed in |
|---|---|---|---|---|---|
| CVE-2022-31037 | OroCommerce Cross site scripting vulnerability during shipping rule editing for UPS integration | medium | 6.9 | >=4.1.0 and <5.0.6 | 5.0.6 |
| CVE-2023-32065 | OroCommerce get-totals-for-checkout API endpoint returns unwanted data | medium | 5.8 | >=4.2.0 and <=4.2.10 or >=5.0.0 and <5.0.11 or >=5.1.0 and <5.1.1 | 5.0.11, 5.1.1 |
| CVE-2022-35950 | OroCommerce Cross-site Scripting vulnerability in add note dialog of Shopping List line item | medium | 4.8 | >=4.1.0 and <=4.1.13 or >=4.2.0 and <=4.2.10 or >=5.0.0 and <5.0.11 or >=5.1.0 and <5.1.1 | 5.0.11, 5.1.1 |
| GHSA-6f85-3f8q-qc94 | OroCommerce vulnerable to XSS when adding class name to Selector Manager on pages that use GrapeJS editor | medium | 6.9 | >=5.0 and <5.0.4 | 5.0.4 |
Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.
# one-time install pip install phpwarden # then phpwarden deps composer.lock
Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command
Install docs How findings are ranked