pimcore/admin-ui-classic-bundle Unverified Password Change

Exploitation

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

CVSS

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

EPSS

• CVE-2023-5844: 0.67% estimated exploitation activity in the next 30 days; percentile 51.94 (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 As old password can be set as new password , it is considered as password policy violation. Pimcore is not enforcing strict password policy which allow attacker to set old password as new password Proof of Concept 1. Go to Admin link 2. login and click on - "User | My Profile". 3. Go to change password now put old password as new password and click save. Patches https://github.com/pimcore/admin-ui-classic-bundle/commit/498ac77e54541177be27b0c710e387c47b3836ea.patch Workarounds Update to version 1.2.0 or apply this patches manually https://github.com/pimcore/admin-ui-classic-bundle/commit/498ac77e54541177be27b0c710e387c47b3836ea.patch References https://huntr.com/bounties/b031199d-192a-46e5-8c02-f7284ad74021/

Published by the source

31 Oct 2023, 22:23 UTC

Last modified by the source

10 Nov 2025, 21:56 UTC

Source last checked

26 Oct 2026, 14:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6f58-j323-6472

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

# Patch Next advisory brief: CVE-2023-5844

Advisory: pimcore/admin-ui-classic-bundle Unverified Password Change
IDs: CVE-2023-5844, GHSA-6f58-j323-6472
Record: https://patchnext.com/advisories/cve-2023-5844 (revision 1, source checked 26 Oct 2026, 14:34 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/admin-ui-classic-bundle 1.2.0-RC1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist pimcore/admin-ui-classic-bundle: affected < 1.2.0-RC1; fixed in 1.2.0-RC1

## Suggested inspection (read-only)
- Packagist pimcore/admin-ui-classic-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/admin-ui-classic-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-6f58-j323-6472 (GitHub-reviewed advisory GHSA-6f58-j323-6472 lists affected ranges: Packagist pimcore/admin-ui-classic-bundle >=0 <1.2.0-RC1)

Commands are suggestions: review each one before running it.