The fix for GHSA-4jjr-vmv7-wh4w was incomplete. It addressed the issue in the query builder, but the same protection was not applied to in-memory collection sorting. Manipulating sort parameters could result in the loss of content and assets.
This requires a front-end template that passes request input into a tag's sort parameter. It is not exploitable by default — a template would need to be explicitly set up to sort by a visitor-controlled value.
This has been fixed in 5.73.23 and 6.20.0.
{
"nvd_published_at": "2026-06-19T18:16:19Z",
"cwe_ids": [
"CWE-470"
],
"github_reviewed": true,
"severity": "HIGH",
"github_reviewed_at": "2026-06-26T22:15:47Z"
}