CVE-2025-43712: generator-jhipster · Improper Access Control
Affects generator-jhipsterSource CVE Database V5
Not known to be exploited · CVSS 8.0 High : upgrade to 8.9.0 soon.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.9.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade jhipster/generator-jhipster to 8.9.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubjhipster/generator-jhipsterpkg:github/jhipster/generator-jhipsterOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-43712, European organizations should take the following specific actions: 1) Upgrade JHipster to version 8.9.0 or later as soon as it becomes available, as this version addresses the privilege escalation flaw. 2) Until a patch is applied, implement server-side validation of the 'authorities' parameter to ensure that user roles cannot be altered via client-side manipulation. This includes enforcing strict authorization checks on all endpoints that rely on user roles. 3) Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests attempting to modify role parameters. 4) Conduct thorough code reviews and penetration testing focused on access control mechanisms within JHipster applications. 5) Monitor application logs for anomalous behavior indicative of privilege escalation attempts, such as unexpected admin-level access from standard user accounts. 6) Educate developers and administrators about secure coding practices related to role management and parameter validation. 7) Implement multi-factor authentication (MFA) for administrative access to add an additional security layer. 8) Restrict administrative functionalities to trusted networks or VPNs where feasible to reduce exposure. These targeted measures go beyond generic advice by focusing on the specific vulnerability vector and the architecture of JHipster applications.
Description
JHipster before v.8.9.0 allows privilege escalation via a modified authorities parameter. Upon registering in the JHipster portal and logging in as a standard user, the authorities parameter in the response from the api/account endpoint contains the value ROLE_USER. By manipulating the authorities parameter and changing its value to ROLE_ADMIN, the privilege is successfully escalated to an Admin level. This allowed the access to all admin-related functionalities in the application.