CVE-2026-92692: Sulu JCR-SQL2 Injection Vulnerability

MODERATE
Advisory Identifier: GHSA-jg26-q8hg-3pq4
Share
CWE-89
Published
Advisory Summary

CVE-2026-92692 is a MODERATE jcr-sql2 injection vulnerability (CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')) affecting Sulu libraries in the Packagist ecosystem. The issue involves jcr-sql2 injection via `categories` query parameter (unauthenticated). Remediation is available by upgrading affected packages to version 2.6.25, 3.0.8.

CVE-2026-92692 at a Glance

CVE Identifier CVE-2026-92692
GHSA Identifier GHSA-jg26-q8hg-3pq4
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Affected Product Sulu
Package Ecosystem Packagist
Published Date
Last Updated

How to Fix CVE-2026-92692

To remediate this vulnerability, upgrade all affected Sulu dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

sulu/sulu fixed: 2.6.25 
Upgrade sulu/sulu to 2.6.25
sulu/sulu fixed: 3.0.8 
Upgrade sulu/sulu to 3.0.8
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for sulu/sulu

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-92692, inspect your project dependencies for Sulu:

inspect dependencies for sulu/sulu

Analyze the terminal output to locate any version of Sulu in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.6.25), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'), where the product constructs all or part of an sql command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended sql command when it is sent to a downstream component. without sufficient removal or quoting of sql syntax in user-controllable inputs, the generated sql query can cause those inputs to be interpreted as sql instead of ordinary user data. In Sulu, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

CVE-2026-92692 Affected Sulu Versions

2 component(s)
Fixed Versions:
2.6.253.0.8
Product / Package Ecosystem Affected Versions Fixed Version
sulu/sulu
 Packagist
< 2.6.25
2.6.25
sulu/sulu
 Packagist
≥ 3.0.0
< 3.0.8
3.0.8

References

GitHub Advisory / Wiki ADVISORY
https://github.com/sulu/sulu/security/advisories/GHSA-jg26-q8hg-3pq4
Security Fix Commit FIX COMMIT
https://github.com/sulu/sulu/commit/d19c01487af8c3de2fb3aa145856707a6367392c
Sulu Source Repository REPOSITORY
https://github.com/sulu/sulu
Sulu Release RELEASE
https://github.com/sulu/sulu/releases/tag/2.6.25
Sulu Release RELEASE
https://github.com/sulu/sulu/releases/tag/3.0.8

Frequently Asked Questions

What is CVE-2026-92692?
CVE-2026-92692 is a security vulnerability in Sulu involving JCR-SQL2 injection via `categories` query parameter (unauthenticated) under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection').
Which Sulu versions are affected?
Affected versions include releases prior to 2.6.25, 3.0.8 across affected packages: sulu/sulu.
What version fixes CVE-2026-92692?
Upgrading to 2.6.25, 3.0.8 (or the latest patched release for your respective branch) resolves the vulnerability.
Is sulu/sulu affected?
Yes, sulu/sulu is affected in releases prior to 2.6.25, 3.0.8. Upgrade your dependency to 2.6.25, 3.0.8 or later.
What CWE is associated with CVE-2026-92692?
CVE-2026-92692 is classified under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.).
How can I check Packagist dependencies for CVE-2026-92692?
Run the dependency tree command: 'inspect dependencies for sulu/sulu'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-jg26-q8hg-3pq4",
  "modified" : "2026-09-23T18:21:22Z",
  "published" : "2026-09-23T18:21:22Z",
  "aliases" : [ "CVE-2026-92692" ],
  "summary" : "Sulu: JCR-SQL2 injection via `categories` query parameter (unauthenticated)",
  "details" : "### Impact\n\nAn unauthenticated JCR-SQL2 injection exists in the Smart Content category filter of the 2.x content query builder.\n\nCategory 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.\n\nAn anonymous visitor can therefore:\n\n- 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\n- submit malformed query fragments that cause query errors or resource-intensive queries, degrading availability.\n\nBecause 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.\n\n### Patches\n\nFixed 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.\n\n### Workarounds\n\nIf you cannot upgrade immediately:\n\n- 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.\n- Alternatively, disable category filtering on publicly reachable Smart Content elements until the patch is applied.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "sulu/sulu"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.6.25"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "sulu/sulu"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.0.0"
      }, {
        "fixed" : "3.0.8"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/sulu/sulu/security/advisories/GHSA-jg26-q8hg-3pq4"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/sulu/sulu/commit/d19c01487af8c3de2fb3aa145856707a6367392c"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/sulu/sulu"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/sulu/sulu/releases/tag/2.6.25"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/sulu/sulu/releases/tag/3.0.8"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-89" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-23T18:21:22Z",
    "nvd_published_at" : null
  }
}