Storefront user can access history and most viewed data from matching back-office user with the same IDGHSA-v7px-46v9-5qwp
MEDIUMFix: oroinc/orocommerce@41c5264GHSA-v7px-46v9-5qwp is a medium-severity (CVSS 4.3) Information Exposure vulnerability in oro/customer-portal. A fix is available for oro/customer-portal — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-v7px-46v9-5qwp.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
oro/customer-portal🐘oro/customer-portal🐘oro/customer-portal🐘oro/customer-portalReal-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
OroPlatform is a PHP Business Application Platform (BAP). Navigation history, most viewed and favorite navigation items are returned to storefront user in JSON navigation response if ID of storefront user matches ID of back-office user. This vulnerability is fixed in 5.1.4.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | oro/customer-portal | ≥ 4.1.0 | No fix |
| 🐘Packagist | oro/customer-portal | ≥ 4.2.0 | No fix |
| 🐘Packagist | oro/customer-portal | ≥ 5.0.0 | No fix |
| 🐘Packagist | oro/customer-portal | ≥ 5.1.0&&< 5.1.4 | 5.1.4composer require oro/customer-portal:^5.1.4 |
Affected Products
oroplatformoroincDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for oro/customer-portal, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for GHSA-v7px-46v9-5qwp; check the affected-versions list above or the advisory for the patched release of oro/customer-portal, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is GHSA-v7px-46v9-5qwp in your dependencies?
Find it across Packagist, including transitive dependencies.