{{ message }}
[GHSA-vg3j-hpm9-8v5v] Craft CMS has a potential information disclosure vulnerability in preview tokens - #9301
Merged
advisory-database[bot] merged 1 commit intoSep 2, 2026
Conversation
Collaborator
github-actions
Bot
changed the base branch from
main
to
nikpivkin/advisory-improvement-9301
September 1, 2026 14:30
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The corrected boundaries match the referenced releases, and the shortened CVSS vector preserves its meaning.
Pull request overview
Corrects Craft CMS affected-version boundaries and normalizes the CVSS v4 vector.
Changes:
- Sets patched versions to 4.17.3 and 5.9.7.
- Removes obsolete affected-range metadata.
- Removes redundant
Not DefinedCVSS metrics.
File summaries
| File | Description |
|---|---|
GHSA-vg3j-hpm9-8v5v.json |
Aligns affected ranges, fixes, and CVSS data. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
angrybrad
suggested changes
Sep 1, 2026
angrybrad
left a comment
angrybrad
left a comment
There was a problem hiding this comment.
The version 4.17.3 fix is correct, but there is no 5.9.7 fix and there should be.
| ], | ||
| "database_specific": { | ||
| "last_known_affected_version_range": "< 4.17.3" | ||
| } |
| ], | ||
| "database_specific": { | ||
| "last_known_affected_version_range": "< 5.9.6" | ||
| } |
There was a problem hiding this comment.
Why was this deleted instead of being changed to "< 5.9.7"?
advisory-database
Bot
merged commit Sep 2, 2026
56f4eec
into
nikpivkin/advisory-improvement-9301
5 checks passed
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates
Comments
Both entries need a small change.
The 4.x entry has the range
>= 4.0.0-RC1, < 4.17.3and4.17.4as the first patched version. The fix shipped in 4.17.3, so the first patched version should be4.17.3. The range is already correct.The 5.x entry has the range
>= 5.0.0-RC1, < 5.9.6and5.9.7as the first patched version. On this branch the fix shipped in 5.9.7, so 5.9.6 is still affected and the range should be>= 5.0.0-RC1, < 5.9.7. The first patched version is already correct.Evidence: the advisory links the fix commit craftcms/cms@6a88468. Tag 4.17.2 does not contain it, tag 4.17.3 does. On the 5.x side, tag 5.9.6 does not contain it and tag 5.9.7 does.
Right now the range and the first patched version disagree in both entries, so the OSV export keeps the range in
database_specific.last_known_affected_version_rangeand puts the patched version into thefixedevent. For the 4.x entry that marks 4.17.3 as affected although the fix is in it. After the change the two fields agree and the extra field goes away.One more thing about the CVSS vector. I did not want to change it, but the form refused to submit with "The entered vector string contains an error and cannot populate a score". Shortening the vector to the base metrics made the form accept it. The dropped part was only metrics set to
Not Defined, so the score stays 2.3.