How severe is GHSA-v7px-46v9-5qwp?

GHSA-v7px-46v9-5qwp has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-v7px-46v9-5qwp?

GHSA-v7px-46v9-5qwp affects the following packages: oro/customer-portal (Packagist), oro/customer-portal (Packagist), oro/customer-portal (Packagist), oro/customer-portal (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-v7px-46v9-5qwp?

No patched version of oro/customer-portal has shipped for GHSA-v7px-46v9-5qwp yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-v7px-46v9-5qwp in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for oro/customer-portal. 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.

How do I mitigate GHSA-v7px-46v9-5qwp if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-v7px-46v9-5qwp?

O3 pinpoints whether GHSA-v7px-46v9-5qwp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-v7px-46v9-5qwp actively exploited in the wild?

No public exploit code has been indexed for GHSA-v7px-46v9-5qwp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-v7px-46v9-5qwp?

GHSA-v7px-46v9-5qwp has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 35th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-v7px-46v9-5qwp?

GHSA-v7px-46v9-5qwp is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-v7px-46v9-5qwp published, and has it been updated?

GHSA-v7px-46v9-5qwp was published on March 25, 2024 and was last updated on March 25, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-v7px-46v9-5qwp

MEDIUM

Storefront user can access history and most viewed data from matching back-office user with the same ID

Also known asCVE-2023-48296

Published

Mar 25, 2024

Updated

Mar 25, 2024

Affected

4 pkgs

Patched

1 / 4

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk35th percentile+0.21%

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.

Blast Radius

4 pkgs affected

🐘oro/customer-portal🐘oro/customer-portal🐘oro/customer-portal🐘oro/customer-portal

Real-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

Impact

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.

Affected Packages

4 total 1 fixed

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.4

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for oro/customer-portal. 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
No patched version of oro/customer-portal has shipped for GHSA-v7px-46v9-5qwp 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 pinpoints whether GHSA-v7px-46v9-5qwp 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-v7px-46v9-5qwp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact 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.

O3 Security · Impact-Aware SCA

Is GHSA-v7px-46v9-5qwp in your dependencies?

O3 detects GHSA-v7px-46v9-5qwp across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works