How severe is GHSA-j65r-g7q2-f8v3?

GHSA-j65r-g7q2-f8v3 has a CVSS score of 6.7/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-j65r-g7q2-f8v3?

GHSA-j65r-g7q2-f8v3 affects the following packages: pimcore/customer-management-framework-bundle (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-j65r-g7q2-f8v3?

Update pimcore/customer-management-framework-bundle to 3.3.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j65r-g7q2-f8v3 is resolved across your whole dependency graph.

How do I detect GHSA-j65r-g7q2-f8v3 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pimcore/customer-management-framework-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-j65r-g7q2-f8v3 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-j65r-g7q2-f8v3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-j65r-g7q2-f8v3 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-j65r-g7q2-f8v3?

GHSA-j65r-g7q2-f8v3 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 46th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-j65r-g7q2-f8v3?

GHSA-j65r-g7q2-f8v3 is classified as CWE-257 (CWE-257), CWE-522 (CWE-522). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-j65r-g7q2-f8v3 published, and has it been updated?

GHSA-j65r-g7q2-f8v3 was published on May 25, 2023 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

Pimcore customers' list user password hash is disclosedGHSA-j65r-g7q2-f8v3

MEDIUMFix: pimcore/customer-data-framework@d1d58c1

GHSA-j65r-g7q2-f8v3 is a medium-severity (CVSS 6.7) CWE-257 vulnerability in pimcore/customer-management-framework-bundle. A fix is available for pimcore/customer-management-framework-bundle — see the affected versions and patch details below.

Also known asCVE-2023-2881

Published

May 25, 2023

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-j65r-g7q2-f8v3.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs46th percentile — riskier than 46% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘pimcore/customer-management-framework-bundle

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

The customer view exposes the hashed password along with other deails. An attacker is then able to enum password of a particular id, likewise we can replace id with other user , for example 1015, password hash can be disclosed which can be further cracked with hashcat

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`pimcore/customer-management-framework-bundle`	all versions	3.3.10`composer require pimcore/customer-management-framework-bundle:^3.3.10`

Affected Products

1 product · 1 configurations

Application

customer management frameworkpimcore

< 3.3.10

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pimcore/customer-management-framework-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pimcore/customer-management-framework-bundle to 3.3.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j65r-g7q2-f8v3 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact The customer view exposes the hashed password along with other deails. An attacker is then able to enum password of a particular id, likewise we can replace id with other user , for example 1015, password hash can be disclosed which can be further cracked with hashcat ### Patches Update to version 3.3.10 or apply this patch manually https://github.com/pimcore/customer-data-framework/commit/d1d58c10313f080737dc1e71fab3beb12488a1e6.patch ### Workarounds Apply https://github.com/pimcore/customer-data-framework/commit/d1d58c10313f080737dc1e71fab3beb12488a1e6.patch manually. ### Refer