# CVE-2023-48296: OroPlatform's storefront user can access history and most viewed data from matching back-office user with the same ID

> Storefront users can access back-office navigation history and most viewed data if their user IDs match, exposing internal usage patterns.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Mar 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-v7px-46v9-5qwp

## What is CVE-2023-48296?

CVE-2023-48296 is a medium-severity vulnerability in oroinc orocommerce, published on 25 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-48296?

8 open source packages ship an affected version, including oro/customer-portal. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `oro/customer-portal` | Packagist | From 4.1.0 to 4.1.13 | None |
| `oro/customer-portal` | Packagist | From 4.1.0 to 4.1.13 | None |
| `oro/customer-portal` | Packagist | From 4.2.0 to 4.2.10 | None |
| `oro/customer-portal` | Packagist | From 4.2.0 to 4.2.10 | None |
| `oro/customer-portal` | Packagist | From 5.0.0 to 5.0.11 | None |
| `oro/customer-portal` | Packagist | From 5.0.0 to 5.0.11 | None |
| `oro/customer-portal` | Packagist | From 5.1.0 | 5.1.4 |
| `oro/customer-portal` | Packagist | From 5.1.0 | 5.1.4 |

Products: Oroinc Oroplatform.

## How do I fix CVE-2023-48296?

Upgrade oro/customer-portal to 5.1.4 or later.

## Is CVE-2023-48296 being exploited?

There is no known exploitation of CVE-2023-48296 in the wild and no public exploit code.

## Other vulnerabilities in oroinc orocommerce

- [CVE-2021-43852](https://insights.sbomify.com/CVE-2021-43852/): JavaScript Prototype Pollution in oro/platform (high 8.8)
- [CVE-2022-41951](https://insights.sbomify.com/CVE-2022-41951/): OroPlatform vulnerable to path traversal during temporary file manipulations (high 8.6)
- [CVE-2021-41236](https://insights.sbomify.com/CVE-2021-41236/): XSS vulnerability in oro/platform (medium 6.9)
- [CVE-2024-50677](https://insights.sbomify.com/CVE-2024-50677/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2023-32062](https://insights.sbomify.com/CVE-2023-32062/): OroCalendarBundle has incorrect system calendar events visibility (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-48296 and fix it if it is affected.

What it is: CVE-2023-48296 is a medium-severity vulnerability in oroinc orocommerce, published on 25 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-48296 in the wild and no public exploit code.

Affected packages and fixed versions:
- oro/customer-portal (Packagist): affected from 4.1.0 up to 4.1.13; no fix listed
- oro/customer-portal (Packagist): affected from 4.1.0 up to 4.1.13; no fix listed
- oro/customer-portal (Packagist): affected from 4.2.0 up to 4.2.10; no fix listed
- oro/customer-portal (Packagist): affected from 4.2.0 up to 4.2.10; no fix listed
- oro/customer-portal (Packagist): affected from 5.0.0 up to 5.0.11; no fix listed
- oro/customer-portal (Packagist): affected from 5.0.0 up to 5.0.11; no fix listed
- oro/customer-portal (Packagist): affected from 5.1.0; fixed in 5.1.4
- oro/customer-portal (Packagist): affected from 5.1.0; fixed in 5.1.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-48296/ (Markdown: https://insights.sbomify.com/CVE-2023-48296/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-48296
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-48296
- OSV: https://osv.dev/vulnerability/CVE-2023-48296

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-48296/
Summaries are generated and may contain mistakes; the official description above is the record.