Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-107375 high CVSS 8.8

SQL Injection in generator-jhipster (CVE-2026-107375)

Summary

SQL injection in generator-jhipster (CVE-2026-107375). Successful exploitation can lead to full system takeover. Exploitable via GET /api/. Mitigation: upgrade to 9.4.0 or later.

Original description

The description as published by the source.

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 EntityManager_reactive.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/?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 arbitrary SQL: read any table (including jhi_user password hashes), modify or delete data, and drop tables (full C/I/A impact). Independently reproduced end-to-end on the default dev database (H2) and the default production database (PostgreSQL 16).

The JPA (non-reactive) path is not affected: Spring Data JPA validates sort property names against the entity metamodel. NoSQL backends are out of scope of this root cause.

2. Root Cause

The generator t…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-107375 has been found in generator-jhipster.
Attackers can target a specific entry point like GET /api/ over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade generator-jhipster to 9.4.0 or later.
If unsure, ask your IT team or search "generator-jhipster CVE-2026-107375" on the vendor's site.

CVE-2026-107375 (generator-jhipster) — CWE-89 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/ / sort / EntityManager_reactive.java.ejs / jhi_user
Patched: 9.4.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SQL injection (CWE-89) exists in generator-jhipster. Attackers reach the vulnerable code path via GET /api/.

📍 Affected scope

Check the vendor advisory for the affected versions of generator-jhipster. Attack surface: GET /api/ / sort / EntityManager_reactive.java.ejs / jhi_user.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 9.4.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /api/ requests with malformed payloads or SQL meta-characters. Run grep -r 'generator-jhipster' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'generator-jhipster' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で generator-jhipster を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /api/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /api/ への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade generator-jhipster to 9.4.0

    ステージング環境で 9.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against GET /api/ on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm generator-jhipster
[{"type":"SEMVER","events":[{"introduced":"7.0.0"},{"fixed":"9.4.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details