JHipster: SQL Injection in the Parameter of JHipster-Generated Reactive (WebFlux + R2DBC) Applicationssort
CVE-2026-107375GHSA-r223-96jv-q533
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (generator-jhipster 9.4.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- >= 7.0.0, < 9.4.0
- Fixed in
- 9.4.0
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-r223-96jv-q533 lists affected ranges: npm generator-jhipster >=7.0.0 <9.4.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-r223-96jv-q533 lists affected ranges: npm generator-jhipster >=7.0.0 <9.4.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS
- CVE-2026-107375: 0.43% estimated exploitation activity in the next 30 days; percentile 37.60 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
SQL Injection in the sort Parameter of JHipster-Generated Reactive (WebFlux + R2DBC) Applications - Product: jhipster/generator-jhipster (npm package generator-jhipster) - Affected versions: v7.0.0 through v9.2.0 - Component: generated reactive-application code, template EntityManagerreactive.java.ejs - Report date: 2026-08-29 --- 1. Summary Every reactive (Spring WebFlux + Spring Data R2DBC + SQL) application generated by generator-jhipster contains an SQL injection in the paginated entity list endpoints (GET /api/<entity?sort=...). The sort request parameter is taken verbatim from the user and concatenated into the SQL ORDER BY clause without quoting or validation. Because the generated query has no bound parameters, the R2DBC drivers execute it via the simple query protocol, so ;-separated extra statements are run against the database. A single authenticated low-privileged user (including an account obtained through the default self-registration flow) can therefore execute…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-r223-96jv-q533
- Revision 2 · amended ·
Amended from osv record GHSA-r223-96jv-q533
- Revision 1 · created ·
Published from ghsa record GHSA-r223-96jv-q533
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-107375 Advisory: JHipster: SQL Injection in the Parameter of JHipster-Generated Reactive (WebFlux + R2DBC) Applicationssort IDs: CVE-2026-107375, GHSA-r223-96jv-q533 Record: https://patchnext.com/advisories/cve-2026-107375 (revision 3, source checked 26 Oct 2026, 13:07 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: generator-jhipster 9.4.0. A vendor fix does not mean a deployment is fixed. ## Affected components - npm generator-jhipster: affected >= 7.0.0, < 9.4.0; fixed in 9.4.0 ## Suggested inspection (read-only) - `npm ls generator-jhipster --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on generator-jhipster. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-r223-96jv-q533 (GitHub-reviewed advisory GHSA-r223-96jv-q533 lists affected ranges: npm generator-jhipster >=7.0.0 <9.4.0) - Verified: https://osv.dev/vulnerability/GHSA-r223-96jv-q533 (OSV record GHSA-r223-96jv-q533 lists affected ranges: npm generator-jhipster >=7.0.0 <9.4.0 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…