Pimcore Web2Print Tools Bundle "Favourite Output Channel Configuration" Missing Function Level Authorization
CVE-2026-23496GHSA-4wg4-p27p-5q2r
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (pimcore/web2print-tools-bundle 6.1.1, 5.2.2), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist pimcore/web2print-tools-bundle
- Affected
- >= 6.0.0-RC1, <= 6.1<= 5.2.1
- Fixed in
- 5.2.2, 6.1.1
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-4wg4-p27p-5q2r lists affected ranges: Packagist pimcore/web2print-tools-bundle >=6.0.0-RC1 =0 <=5.2.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
- EPSS
- CVE-2026-23496: 0.29% estimated exploitation activity in the next 30 days; percentile 21.37 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary The application fails to enforce proper server-side authorization checks on the API endpoint responsible for managing "Favourite Output Channel Configurations." Testing revealed that an authenticated backend user without explicitely lacking permissions for this feature was still able to successfully invoke the endpoint and modify or retrieve these configurations. This violates the principle of least privilege and constitutes a classic example of Broken Access Control (OWASP Top 10 A01:2021). Because authorization is not validated at the function level, any authenticated user can perform actions intended only for privileged roles, leading to horizontal or vertical privilege escalation. Detail The backend user without permission was still able to list, create, update "Favourite Output Channel Configuration" item Step to Reproduce the issue login as Admin (full permission) and clicked "Favourite Output Channel Configurations" <img width="949" height="860" alt="Screenshot…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-4wg4-p27p-5q2r
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-23496 Advisory: Pimcore Web2Print Tools Bundle "Favourite Output Channel Configuration" Missing Function Level Authorization IDs: CVE-2026-23496, GHSA-4wg4-p27p-5q2r Record: https://patchnext.com/advisories/cve-2026-23496 (revision 1, source checked 26 Oct 2026, 14:35 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.4) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: pimcore/web2print-tools-bundle 6.1.1, 5.2.2. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist pimcore/web2print-tools-bundle: affected >= 6.0.0-RC1, <= 6.1; <= 5.2.1; fixed in 5.2.2, 6.1.1 ## Suggested inspection (read-only) - Packagist pimcore/web2print-tools-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/web2print-tools-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-4wg4-p27p-5q2r (GitHub-reviewed advisory GHSA-4wg4-p27p-5q2r lists affected ranges: Packagist pimcore/web2print-tools-bundle >=6.0.0-RC1 =0 <=5.2.1) Commands are suggestions: review each one before running it.
Loading voting…