Pimcore vulnerable to Business Logic Errors via Customer automation rules

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

EPSS

• CVE-2023-32075: 0.76% estimated exploitation activity in the next 30 days; percentile 55.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Business Logic Errors 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. Patches Update to version 3.3.9 or apply this patch manually https://github.com/pimcore/customer-data-framework/commit/e3f333391582d9309115e6b94e875367d0ea7163.patch Workarounds Apply https://github.com/pimcore/customer-data-framework/commit/e3f333391582d9309115e6b94e875367d0ea7163.patch manually. References https://huntr.dev/bounties/cecd7800-a996-4f3a-8689-e1c2a1e0248a/

Published by the source

11 May 2023, 16:39 UTC

Last modified by the source

10 Nov 2023, 05:01 UTC

Source last checked

26 Oct 2026, 14:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-x99j-r8vv-gwwj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-32075

Advisory: Pimcore vulnerable to Business Logic Errors via Customer automation rules
IDs: CVE-2023-32075, GHSA-x99j-r8vv-gwwj
Record: https://patchnext.com/advisories/cve-2023-32075 (revision 1, source checked 26 Oct 2026, 14:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pimcore/customer-management-framework-bundle 3.3.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist pimcore/customer-management-framework-bundle: affected < 3.3.9; fixed in 3.3.9

## Suggested inspection (read-only)
- Packagist pimcore/customer-management-framework-bundle: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pimcore/customer-management-framework-bundle.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-x99j-r8vv-gwwj (GitHub-reviewed advisory GHSA-x99j-r8vv-gwwj lists affected ranges: Packagist pimcore/customer-management-framework-bundle >=0 <3.3.9)

Commands are suggestions: review each one before running it.