CVE-2026-107375
Received Received - Intake

SQL Injection in JHipster Reactive Applications via ORDER BY Clause

Publication date: 2026-10-08

Last updated on: 2026-10-08

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-08
Last Modified
2026-10-08
Generated
2026-10-08
AI Q&A
2026-10-08
EPSS Evaluated
N/A
NVD
CVE-2026-107375
EUVD
EUVD-2026-95130

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
jhipster generator-jhipster >= 7.0.0, < 9.4.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 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.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects JHipster applications using Spring WebFlux, Spring Data R2DBC, and SQL databases. It allows authenticated users to inject malicious SQL queries via the sort parameter in paginated endpoints. The generated code inserts user input directly into SQL ORDER BY clauses without validation, enabling attackers to execute additional SQL statements separated by semicolons. This can lead to unauthorized data access, modification, or deletion.

Detection Guidance

This vulnerability affects JHipster applications using Spring WebFlux, Spring Data R2DBC, and SQL databases. Check if your application uses these components and is running a version between 7.0.0 and 9.4.0. Inspect generated EntityManager_reactive.java files for unvalidated sort parameters passed to SQL ORDER BY clauses.

Impact Analysis

If you use a vulnerable JHipster application, an attacker with valid credentials could read sensitive data, alter or delete records, or drop entire database tables. This could disrupt operations, leak confidential information, or cause data loss. Non-reactive JPA applications and NoSQL backends are not affected.

Compliance Impact

This vulnerability could lead to violations of GDPR (data breaches), HIPAA (unauthorized access to health data), or other regulations requiring data protection. Unauthorized data exposure or modification may result in legal penalties, reputational damage, and loss of compliance certifications.

Mitigation Strategies

Upgrade JHipster to version 9.4.0 or later. If upgrading is not immediately possible, disable reactive endpoints or apply input validation to sort parameters before they reach the SQL ORDER BY clause. Review database permissions to limit exposure.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-107375. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart