Summary
Craft CMS: Authorized asset "preview file" requests bypass allows users without asset access to retrieve private preview metadata
An authenticated low-privileged user can call assets/preview-file for an asset they are not authorized to view and still receive preview response data (previewHtml) for that private asset.
The returned preview HTML included a private preview image route containing the target private assetId, even though canView was false for the attacker account.
Details
assets/preview-fileaccepts a maliciously controlledassetIdand renders preview output.- The action does not enforce per-asset view authorization prior to returning preview content.
- As a result, an authenticated user without asset-view permission can still obtain private preview output.
This affects Craft installations with authenticated users of mixed privilege levels with private assets.
Resources
- d30df3112220db1ffd6726a3ed11857014c7fb27
- b1cddf72c98a
Impact
The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.
Affected versions
Security releases
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
craftcms/cms to 5.9.14 or later; craftcms/cms to 4.17.8 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-44PX-QJJC-XRHQ? GHSA-44PX-QJJC-XRHQ is a low-severity missing authorization vulnerability in craftcms/cms (composer), affecting versions >= 5.0.0-RC1, <= 5.9.13. It is fixed in 5.9.14, 4.17.8. The application does not perform an authorization check before performing a sensitive operation.
- Which versions of craftcms/cms are affected by GHSA-44PX-QJJC-XRHQ? craftcms/cms (composer) versions >= 5.0.0-RC1, <= 5.9.13 is affected.
- Is there a fix for GHSA-44PX-QJJC-XRHQ? Yes. GHSA-44PX-QJJC-XRHQ is fixed in 5.9.14, 4.17.8. Upgrade to this version or later.
- Is GHSA-44PX-QJJC-XRHQ exploitable, and should I be worried? Whether GHSA-44PX-QJJC-XRHQ 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 GHSA-44PX-QJJC-XRHQ 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 GHSA-44PX-QJJC-XRHQ?
- Upgrade
craftcms/cmsto 5.9.14 or later - Upgrade
craftcms/cmsto 4.17.8 or later
- Upgrade