# CVE-2023-32064: OroCommerce Customer Portal Incorrect Customer and Customer Group Frontend Menus pages visibility

> Back-office users can bypass ACL restrictions to view customer and customer group menu information in OroCommerce.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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:** 28 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-8gwj-68w6-7v6c

## What is CVE-2023-32064?

CVE-2023-32064 is a medium-severity missing authorization vulnerability in oroinc orocommerce, published on 28 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OroCommerce package with customer portal and non authenticated visitor website base features. Back-office users can access information about Customer and Customer User menus, bypassing ACL security restrictions due to insufficient security checks. This issue has been patched in version 5.0.11 and 5.1.1.

Weakness: CWE-284 (Improper Access Control)

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

6 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.2.0 to 4.2.8 | None |
| `oro/customer-portal` | Packagist | From 4.2.0 to 4.2.8 | None |
| `oro/customer-portal` | Packagist | From 5.0.0 | 5.0.11 |
| `oro/customer-portal` | Packagist | From 5.0.0 | 5.0.11 |
| `oro/customer-portal` | Packagist | From 5.1.0 | 5.1.1 |
| `oro/customer-portal` | Packagist | From 5.1.0 | 5.1.1 |

Products: Oroinc Orocommerce.

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

Upgrade oro/customer-portal to a fixed version for your release line: 5.0.11 or 5.1.1.

## Is CVE-2023-32064 being exploited?

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

## Other vulnerabilities in oroinc orocommerce

- [CVE-2022-35950](https://insights.sbomify.com/CVE-2022-35950/): OroCommerce Cross-site Scripting vulnerability in add note dialog of Shopping List line item (medium 6.9)
- [CVE-2022-31037](https://insights.sbomify.com/CVE-2022-31037/): OroCommerce vulnerable to Cross-site Scripting via Shipping rule editing page (medium 6.9)
- [CVE-2023-32065](https://insights.sbomify.com/CVE-2023-32065/): OroCommerce get-totals-for-checkout API endpoint returns unwanted data (medium 5.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-32064 is a medium-severity missing authorization vulnerability in oroinc orocommerce, published on 28 Nov 2023. 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-32064 in the wild and no public exploit code.

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

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-32064/ (Markdown: https://insights.sbomify.com/CVE-2023-32064/index.md)
```

## Sources

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

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