[GHSA-4f5x-q4jc-xfcf] pimcore/pimcore: patched version predates the fix (first fixed release: 10.2.9) - #9384
Open
zyl71 wants to merge 1 commit into
Conversation
…ix (first fixed release: 10.2.9)
github-actions
Bot
changed the base branch from
main
to
zyl71/advisory-improvement-9384
September 7, 2026 04:28
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
Current record: Packagist:pimcore/pimcore: introduced=0 fixed=10.2.7
Proposed: Packagist:pimcore/pimcore: introduced=0 fixed=10.2.9
The record's fixed version 10.2.7 (released 2021-12-22) predates the fix: the media-query-name validation was committed 2022-01-17 (6f36e841) and merged into the 10.2 branch as 62d6ca67 (PR #11207) on 2022-01-19, and the Packagist dist shas of 10.2.7 (82dae690) and 10.2.8 (a23ccb2b) do not contain it. 10.2.9 (2022-01-19) is the first release with the code (the same release also adds htmlspecialchars on thumbnail group names). No other release line was active (6.9.x ended June 2021), so 0 -> 10.2.9 is right.
Release lines: Only the 10.2.x line was receiving releases around the fix (10.2.6 2021-12-09 ... 10.2.10 2022-02-02); it is fixed at 10.2.9. 10.3.0 (2022-02-02) contains the fix (compare v10.3.0...62d6ca67 = behind). The 6.9.x line ended with 6.9.6 on 2021-06-23, before the fix, so it stays entirely affected and is covered by 0 -> 10.2.9. No other line existed.
Upstream statements: on the huntr report the maintainer "marked this as fixed in 10.2.7 with commit 6f36e8", and the CVE-2022-0262 description says "prior to 10.2.7". Both are contradicted by the artifacts: 10.2.7 (2021-12-22) and 10.2.8 (2022-01-05) were published before the fix commit existed (2022-01-17) and neither contains the validation code; the first release carrying it is 10.2.9 (2022-01-19).
Evidence:
Version checks:
This comes from a systematic comparison of advisory ranges with fix commits and published registry artifacts. Happy to adjust if the maintainers intend otherwise.