# CVE-2023-32075: Pimcore vulnerable to Business Logic Errors in Customer automation rules

> Attackers can exploit negative counter values in customer automation rules to bypass intended business logic constraints.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 11 May 2023
- **Updated:** 24 Jan 2025
- **Also known as:** GHSA-x99j-r8vv-gwwj

## What is CVE-2023-32075?

CVE-2023-32075 is a medium-severity vulnerability in pimcore customer-data-framework, published on 11 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Customer Management Framework (CMF) for Pimcore adds functionality for customer data management. In `pimcore/customer-management-framework-bundle` prior to version 3.3.9, business logic errors are possible in the `Conditions` tab since the counter can be a negative number. This vulnerability is capable of the unlogic in the counter value in the Conditions tab. Users should update to version 3.3.9 to receive a patch or, as a workaround, or apply the patch manually.

Weakness: CWE-20 (Improper Input Validation)

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

2 open source packages ship an affected version, including pimcore/customer-management-framework-bundle. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pimcore/customer-management-framework-bundle` | Packagist | All versions | 3.3.9 |
| `pimcore/customer-management-framework-bundle` | Packagist | All versions | 3.3.9 |

Products: Pimcore Customer Management Framework.

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

Upgrade pimcore/customer-management-framework-bundle to 3.3.9 or later.

## Is CVE-2023-32075 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-32075 exists.

## Other vulnerabilities in pimcore customer-data-framework

- [CVE-2023-2881](https://insights.sbomify.com/CVE-2023-2881/): Storing Passwords in a Recoverable Format in pimcore/customer-data-framework (medium 6.7)
- [CVE-2024-21666](https://insights.sbomify.com/CVE-2024-21666/): Pimcore Customer Data Framework Improper Access Control allows unprivileged user to access customers duplicates list (medium 6.5)
- [CVE-2024-21667](https://insights.sbomify.com/CVE-2024-21667/): Pimcore Customer Data Framework Improper Access Control allows unprivileged user to access GDPR extracts (medium 6.5)
- [CVE-2023-4145](https://insights.sbomify.com/CVE-2023-4145/): Cross-site Scripting (XSS) - Stored in pimcore/customer-data-framework (medium 6.5)
- [CVE-2023-2756](https://insights.sbomify.com/CVE-2023-2756/): SQL Injection in pimcore/customer-data-framework (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-32075 is a medium-severity vulnerability in pimcore customer-data-framework, published on 11 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-32075 exists.

Affected packages and fixed versions:
- pimcore/customer-management-framework-bundle (Packagist): affected all versions; fixed in 3.3.9
- pimcore/customer-management-framework-bundle (Packagist): affected all versions; fixed in 3.3.9

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

## Sources

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

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