# CVE-2023-32062: OroCalendarBundle has incorrect system calendar events visibility

> Back-office users can access any system calendar event, bypassing ACL restrictions due to insufficient security checks in OroCalendarBundle.

- **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:** 27 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-x2xm-p6vq-482g

## What is CVE-2023-32062?

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

### Official description

OroPlatform is a package that assists system and user calendar management. Back-office users can access information from any system calendar event, bypassing ACL security restrictions due to insufficient security checks. This vulnerability has been patched in version 5.1.1.

Weakness: CWE-284 (Improper Access Control)

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

6 open source packages ship an affected version, including oro/calendar-bundle. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `oro/calendar-bundle` | Packagist | From 4.2.0 to 4.2.6 | None |
| `oro/calendar-bundle` | Packagist | From 4.2.0 to 4.2.6 | None |
| `oro/calendar-bundle` | Packagist | From 5.0.0 | 5.0.7 |
| `oro/calendar-bundle` | Packagist | From 5.0.0 | 5.0.7 |
| `oro/calendar-bundle` | Packagist | From 5.1.0 | 5.1.1 |
| `oro/calendar-bundle` | Packagist | From 5.1.0 | 5.1.1 |

Products: Oroinc Oroplatform.

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

Upgrade oro/calendar-bundle to a fixed version for your release line: 5.0.7 or 5.1.1.

## Is CVE-2023-32062 being exploited?

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

## Other vulnerabilities in oroinc crm

- [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-45824](https://insights.sbomify.com/CVE-2023-45824/): OroPlatform's pinned entity creation form shows pages of other users (medium 4.3)

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- oro/calendar-bundle (Packagist): affected from 4.2.0 up to 4.2.6; no fix listed
- oro/calendar-bundle (Packagist): affected from 4.2.0 up to 4.2.6; no fix listed
- oro/calendar-bundle (Packagist): affected from 5.0.0; fixed in 5.0.7
- oro/calendar-bundle (Packagist): affected from 5.0.0; fixed in 5.0.7
- oro/calendar-bundle (Packagist): affected from 5.1.0; fixed in 5.1.1
- oro/calendar-bundle (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-32062/ (Markdown: https://insights.sbomify.com/CVE-2023-32062/index.md)
```

## Sources

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

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