pimcore/pimcore

CVE-2026-45703

CVE-2026-45703 is a medium-severity incorrect authorization vulnerability in pimcore/pimcore (composer), affecting versions <= 12.3.6. It is fixed in 12.3.7.

Key facts
CVSS score
6.4
Medium
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
pimcore/pimcore
Fixed in
12.3.7
Disclosed
2026

Summary

Summary The WordExport export flow only checks whether the current backend user has the feature permission wordexport. It does not verify access rights on the target element itself. As a result, a low-privileged backend user can export document content even when the user does not have view permission on that document. In the local Docker reproduction, a low-privileged user successfully exported sensitive content from a page the user was not allowed to view: POC-WORDEXPORT-TITLE POC-WORDEXPORT-DESC Root Cause The controller only performs a feature-level permission check before starting the export flow: [TranslationController.php](pimcore-12.3.3/bundles/WordExportBundle/src/Controller/TranslationController.php#L41) TranslationController.php#L44) It then directly resolves the target element from attacker-controlled type/id input: [TranslationController.php](pimcore-12.3.3/bundles/WordExportBundle/src/Controller/TranslationController.php#L56) [TranslationController.php](pimcore-12.3.3/bundles/WordExportBundle/src/Controller/TranslationController.php#L58) For document-like elements such as Page and Snippet, it renders content in an admin context: [TranslationController.php](pimcore-12.3.3/bundles/WordExportBundle/src/Controller/TranslationController.php#L72) TranslationController.php TranslationController.php No object-level authorization check such as isAllowed('view') is enforced on the target element. Affected Scope Based on the source code, the following element types may be affected: page snippet email object For page-like documents, the pimcoreadmin = true rendering context may expose additional backend-visible content. Preconditions The attacker is an authenticated backend user The attacker has the wordexport permission The attacker does not have view permission on the target document Reproduction Environment Reproduction root: pimcore-12.3.3-repro Standalone PoC script: [pocwordexport.php](pimcore-12.3.3-repro/tools/pocwordexport.php) Reproduction Steps Create a low-privileged user named auditorwordexport with only the wordexport permission and no document workspace permissions. Create a test page at /poc-wordexport-secret-page containing sensitive values: title = POC-WORDEXPORT-TITLE description = POC-WORDEXPORT-DESC Verify that the user does not have view permission on that page. Execute wordExportAction() and wordExportDownloadAction() as that user. Check whether the exported HTML contains the sensitive values. Reproduction command: Reproduction Result Relevant PoC output: This shows that: The user cannot view the target page The exported file still contains the page's sensitive content This confirms that the issue is practically exploitable. Security Impact Unauthorized disclosure of structured page fields Unauthorized export of restricted backend content Potential exposure of unpublished or otherwise restricted content Lateral data access by low-privileged backend accounts Remediation Perform object-level authorization immediately after resolving the element from type/id. Require at least view permission on the target element. Apply consistent authorization checks across page, snippet, email, and object. Bind export creation and export download to the requesting user or an equivalent authorization context. Add regression tests to ensure that users with word_export but without element view permission cannot export content.

Impact

What is incorrect authorization?

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

Severity and exposure

CVE-2026-45703 has a CVSS score of 6.4 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (12.3.7). Upgrading removes the vulnerable code path.

Affected versions

composer

  • pimcore/pimcore (<= 12.3.6)

Security releases

  • pimcore/pimcore → 12.3.7 (composer)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-45703 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-45703 is reachable in your applications. Get a demo

Remediation advice

Upgrade pimcore/pimcore to 12.3.7 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-45703

What is CVE-2026-45703?

CVE-2026-45703 is a medium-severity incorrect authorization vulnerability in pimcore/pimcore (composer), affecting versions <= 12.3.6. It is fixed in 12.3.7. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.

How severe is CVE-2026-45703?

CVE-2026-45703 has a CVSS score of 6.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of pimcore/pimcore are affected by CVE-2026-45703?

pimcore/pimcore (composer) versions <= 12.3.6 is affected.

Is there a fix for CVE-2026-45703?

Yes. CVE-2026-45703 is fixed in 12.3.7. Upgrade to this version or later.

Is CVE-2026-45703 exploitable, and should I be worried?

Whether CVE-2026-45703 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-45703 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-45703?

Upgrade pimcore/pimcore to 12.3.7 or later.

Stop the waste.
Protect your environment with Kodem.