CVE-2026-92692: Sulu: JCR-SQL2 injection via `categories` query parameter (unauthenticated)
Impact An unauthenticated JCR-SQL2 injection exists in the Smart Content category filter of the 2.x content query builder. Category IDs supplied through the public ?categories= query parameter are only trimmed and are then concatenated directly into a JCR-SQL2 WHERE clause, without the numeric validation that the equivalent tag filter already performs.
Published Sep 23, 2026
Affected packages
sulu/sulu
- Ecosystem
- Composer (PHP)
- Affected
- < 2.6.25
- Fixed in
- 2.6.25
- Check
composer show sulu/sulu
sulu/sulu
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.0.0, < 3.0.8
- Fixed in
- 3.0.8
- Check
composer show sulu/sulu
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
An unauthenticated JCR-SQL2 injection exists in the Smart Content category filter of the 2.x content query builder.
Category IDs supplied through the public ?categories= query parameter are only trimmed and are then concatenated directly into a JCR-SQL2 WHERE clause, without the numeric validation that the equivalent tag filter already performs. Any public page that renders a Smart Content element with category filtering enabled evaluates this parameter, so no authentication or special configuration beyond a category-filtered content block is required.
An anonymous visitor can therefore:
- inject boolean conditions to infer the existence of, and disclose, content nodes they should not see (for example unpublished pages) via blind boolean-based extraction; and
- submit malformed query fragments that cause query errors or resource-intensive queries, degrading availability.
Because the sink is a JCR-SQL2 query, the impact is limited to reading and enumerating content-repository nodes and to error/denial-of-service conditions; it cannot be used to modify data through this path.
Patches
Fixed in 2.6.25 and 3.0.8. Category, tag, and audience-target-group IDs are now cast to integers before they are used in the JCR-SQL2 query, so no attacker-controlled characters can reach the query.
Workarounds
If you cannot upgrade immediately:
- Apply the fix manually — cast each ID to an integer where it is concatenated into the category (and, defensively, tag and audience-targeting)
WHEREclause in the content Smart Content query builder. - Alternatively, disable category filtering on publicly reachable Smart Content elements until the patch is applied.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-82394
Sulu: Fix authorization bypass when creating preview links
medium5.3Sep 2, 2026CVE-2026-82395
Sulu: Media move/update authorization bypass (IDOR)
medium5.3Sep 2, 2026CVE-2026-82396
Sulu: Stored XSS via media download inline-disposition override
medium5.4Sep 2, 2026CVE-2026-45701
Sulu: Weak Cryptographical usage for API Key generation and Reset Tokens
medium6.9May 18, 2026GHSA-9m6v-8fxc-4r44
Sulu: Used API Keys may be available via Admin API
low2.3May 18, 2026CVE-2026-34372
Sulu checks fix permissions for subentities endpoints
medium5.3Mar 30, 2026
