CVE-2026-92692

Sulu: JCR-SQL2 injection via categories query parameter (unauthenticated)

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) WHERE clause in the content Smart Content query builder.
• Alternatively, disable category filtering on publicly reachable Smart Content elements until the patch is applied.

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.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

Kodem intelligence

Already deployed Kodem?

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.

1. What is CVE-2026-92692? CVE-2026-92692 is a medium-severity SQL injection vulnerability in sulu/sulu (composer), affecting versions < 2.6.25. It is fixed in 2.6.25, 3.0.8. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. Which versions of sulu/sulu are affected by CVE-2026-92692? sulu/sulu (composer) versions < 2.6.25 is affected.
3. Is there a fix for CVE-2026-92692? Yes. CVE-2026-92692 is fixed in 2.6.25, 3.0.8. Upgrade to this version or later.
4. Is CVE-2026-92692 exploitable, and should I be worried? Whether CVE-2026-92692 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2026-92692 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2026-92692?
   • Upgrade sulu/sulu to 2.6.25 or later
   • Upgrade sulu/sulu to 3.0.8 or later

Other vulnerabilities in sulu/sulu