Description
JHipster is a development platform to quickly generate, develop, and deploy modern web applications and microservice architectures. From 7.0.0 until 9.4.0, reactive applications generated with Spring WebFlux, Spring Data R2DBC, and a SQL database pass the attacker-controlled sort request parameter from paginated entity-list endpoints into createOrderByFields in generators/spring-boot/generators/data-relational/templates/src/main/java/package/repository/EntityManager_reactive.java.ejs. The generated code renders these properties into the SQL ORDER BY clause without validation or quoting, and the R2DBC simple query protocol can execute additional statements separated by semicolons. A normal authenticated user can consequently read sensitive tables, modify or delete data, or drop tables, while non-reactive JPA applications and NoSQL backends are outside this root cause. This issue is fixed in 9.4.0.
Published: 2026-10-08
Score: 8.8 High
EPSS: < 1% Very Low
KEV: No
Impact: SQL Injection
Action: Immediate Patch
AI Analysis

Impact

A developed JHipster reactive application may allow an attacker to inject arbitrary SQL through the sort request parameter used in paginated entity-list endpoints. The generator emits code that transmits this raw parameter into an ORDER BY clause without validation or quoting, thereby permitting the injection of additional SQL statements via semicolons. This flaw enables an authenticated user to read, modify, delete, or drop database tables, compromising data confidentiality and integrity.

Affected Systems

Any application produced by the JHipster generator version 7.0.0 through 9.3.x that uses Spring WebFlux, Spring Data R2DBC, and a SQL database is affected. Non‑reactive JPA applications and those with NoSQL backends are not impacted.

Risk and Exploitability

The vulnerability carries a CVSS score of 8.8, indicating high severity. The EPSS score is currently unavailable, and the flaw is not listed in the CISA KEV catalog. Attack requires only authentication and simple manipulation of the sort parameter, making exploitation straightforward. Because the flaw is present in a large generation model, widespread deployment of vulnerable versions raises the likelihood of exploitation.

Generated by OpenCVE AI on October 8, 2026 at 18:22 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to jhipster generator-jhipster version 9.4.0 or later and regenerate the application.
  • Rebuild and redeploy your reactive microservice using the updated generated code.
  • Implement custom validation on the sort request parameter to allow only known columns and prohibit special characters, as a temporary shield until the upgrade is applied.

Generated by OpenCVE AI on October 8, 2026 at 18:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-r223-96jv-q533 JHipster: SQL Injection in the Parameter of JHipster-Generated Reactive (WebFlux + R2DBC) Applicationssort
History

Fri, 09 Oct 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Thu, 08 Oct 2026 19:30:00 +0000

Type Values Removed Values Added
First Time appeared Jhipster
Jhipster generator-jhipster
Vendors & Products Jhipster
Jhipster generator-jhipster

Thu, 08 Oct 2026 17:45:00 +0000

Type Values Removed Values Added
Description JHipster is a development platform to quickly generate, develop, and deploy modern web applications and microservice architectures. From 7.0.0 until 9.4.0, reactive applications generated with Spring WebFlux, Spring Data R2DBC, and a SQL database pass the attacker-controlled sort request parameter from paginated entity-list endpoints into createOrderByFields in generators/spring-boot/generators/data-relational/templates/src/main/java/package/repository/EntityManager_reactive.java.ejs. The generated code renders these properties into the SQL ORDER BY clause without validation or quoting, and the R2DBC simple query protocol can execute additional statements separated by semicolons. A normal authenticated user can consequently read sensitive tables, modify or delete data, or drop tables, while non-reactive JPA applications and NoSQL backends are outside this root cause. This issue is fixed in 9.4.0.
Title JHipster: SQL Injection in the Parameter of JHipster-Generated Reactive (WebFlux + R2DBC) Applicationssort
Weaknesses CWE-89
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}


Subscriptions

Jhipster Generator-jhipster
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-10-09T15:14:52.235Z

Reserved: 2026-10-07T21:07:54.987Z

Link: CVE-2026-107375

cve-icon Vulnrichment

Updated: 2026-10-08T20:58:42.687Z

cve-icon NVD

Status : Undergoing Analysis

Published: 2026-10-08T18:17:21.883

Modified: 2026-10-09T16:17:22.297

Link: CVE-2026-107375

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-08T19:15:20Z

Weaknesses
  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')