CVE-2026-23496
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2026-01-15

Last updated on: 2026-01-15

Assigner: GitHub, Inc.

Description
Pimcore Web2Print Tools Bundle adds tools for web-to-print use cases to Pimcore. Prior to 5.2.2 and 6.1.1, 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 vulnerability is fixed in 5.2.2 and 6.1.1.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-15
Last Modified
2026-01-15
Generated
2026-05-07
AI Q&A
2026-01-16
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 4 associated CPEs
Vendor Product Version / Range
pimcore web2print_tools 5.2.2
pimcore web2print_tools 6.1.1
pimcore web2print_tools to 5.2.2 (exc)
pimcore web2print_tools to 6.1.1 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-284 The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-23496 is a Broken Access Control vulnerability in the Pimcore web2print-tools bundle. It occurs because the application fails to enforce proper server-side authorization checks on the API endpoint that manages 'Favourite Output Channel Configurations.' As a result, authenticated backend users who do not have explicit permissions for this feature can still access, modify, or retrieve these configurations. This happens due to missing permission checks in backend AdminController actions, allowing unauthorized users to perform actions they should not be allowed to. The issue was fixed by adding explicit permission checks in the backend controller methods to ensure only authorized users can perform these actions. [4, 5]


How can this vulnerability impact me? :

This vulnerability can allow unauthorized backend users to list, create, and update 'Favourite Output Channel Configurations' without proper permissions. This can lead to unauthorized manipulation of critical output channels, such as redirecting alerts, suppressing notifications, inserting misleading channels, or gaining insight into internal workflows. Such unauthorized actions can cause operational disruptions, facilitate further attacks through reconnaissance, and potentially violate security policies within an organization. [5]


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability can lead to unauthorized access and modification of sensitive configuration data, which may result in compliance violations with standards like GDPR and HIPAA. Unauthorized manipulation of output channels and exposure of internal workflows can compromise data confidentiality and integrity, potentially breaching regulatory requirements for access control and data protection. [5]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by monitoring API requests to the endpoint managing "Favourite Output Channel Configurations" for unauthorized access attempts. Specifically, you can capture and analyze HTTP requests that list, create, or update these configurations. By replaying these requests using session tokens of backend users who lack the necessary permissions, you can verify if unauthorized access is possible. Commands to capture such traffic could include using tools like curl or wget to send requests with specific cookies and CSRF tokens, or using network traffic analyzers like tcpdump or Wireshark to monitor API calls. For example, a curl command might look like: curl -X GET -H "Cookie: [session cookie]" -H "X-Pimcore-Csrf-Token: [token]" https://your-pimcore-instance/api/favourite-output-channels. If the request succeeds for a user without permissions, the vulnerability exists. [5]


What immediate steps should I take to mitigate this vulnerability?

The immediate mitigation step is to upgrade the pimcore/web2print-tools bundle to version 5.2.2 or later (for the 5.x branch) or 6.1.1 or later (for the 6.x branch), where the vulnerability has been fixed by adding proper permission checks in the AdminController actions. Until the upgrade can be applied, restrict access to the affected API endpoints to only fully trusted backend users and monitor for suspicious activity. Additionally, review and enforce strict permission settings for backend users to minimize the risk of unauthorized access. [1, 2, 4, 5]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart