GHSA-vgjg-248p-rfm2 — craftcms/cms
Fix: craftcms/cms@d30df31GHSA-vgjg-248p-rfm2 is a Information Exposure vulnerability in craftcms/cms. A fix is available for craftcms/cms — see the affected versions and patch details below.
Craft CMS' anonymous "assets/image-editor" calls return private asset editor metadata to unauthorized users
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-vgjg-248p-rfm2.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
craftcms/cms🐘craftcms/cmsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
A low-privileged authenticated user can call assets/image-editor with the ID of a private asset they cannot view and still receive editor response data, including focalPoint.
The endpoint returns private editing metadata without per-asset authorization validation.
Root-cause analysis:
actionImageEditor()acceptsassetIdfrom the request body.- The asset is loaded, and the focal-point data is read.
- Response returns
htmlandfocalPoint. - No explicit authorization check is applied before the response.
Impact
Affected deployments:
- Craft sites where asset edit metadata should remain restricted to authorized users.
Security consequence:
- Unauthorized users can extract private editor metadata and related editor context for inaccessible assets.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | craftcms/cms | ≥ 5.0.0-RC1&&< 5.9.14 | 5.9.14composer require craftcms/cms:^5.9.14 |
| 🐘Packagist | craftcms/cms | ≥ 4.0.0-RC1&&< 4.17.8 | 4.17.8composer require craftcms/cms:^4.17.8 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update craftcms/cms to 5.9.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vgjg-248p-rfm2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vgjg-248p-rfm2 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-vgjg-248p-rfm2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-vgjg-248p-rfm2 in your dependencies?
O3 Security finds GHSA-vgjg-248p-rfm2 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.