Quick answers
- Is CVE-2025-43712 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-43712 being exploited in the wild.
- How severe is CVE-2025-43712?
- Low severity, with a CVSS score of 3.1, published 25 July 2025.
- Which products and versions are affected?
- generator-jhipster (npm) SEMVER:introduced=0,fixed=8.9.0.
- Is there a fix for CVE-2025-43712?
- Yes. generator-jhipster (npm): upgrade to 8.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-43712 attacked?
- It is attacked with local access.
- Am I affected by CVE-2025-43712?
- Check whether you run generator-jhipster (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- generator-jhipster (npm): upgrade to 8.9.0 or later
npm install generator-jhipster@8.9.0
Technical details
The vulnerability was initially reported as an improper access control issue (CWE-284, CWE-451) where the authentication endpoint (/api/account) returned a user's role information (authorities parameter) in the response without proper server-side verification. An attacker could intercept the authentication response, modify the authorities array from ROLE_USER to ROLE_ADMIN, and forward the modified response to the application. The attack required client-side response manipulation (local attack vector), no authentication, and no user interaction. However, the JHipster development team determined through investigation that the original vulnerability report was invalid and withdrew the advisory on 2025-08-04.
Affected products
- JHipster generator-jhipster before 8.9.0
Identifiers
- CVE-2025-43712
- GHSA-cmm8-gw4m-26cw
Timeline
- 2025-07-25: disclosed
- 2025-08-04: advisory: Advisory withdrawn as original report found to be invalid