CVE-2025-43712: High severity JHipster JHipster vulnerability

Published Jul 25, 2025
·
Updated

Withdrawn Advisory This advisory has been withdrawn because the original report was found to be invalid. This link is maintained to preserve external references. For more information, see https://groups.google.com/g/jhipster-dev/c/ATSlWkEjw2w.

Original 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 ROLEUSER. By manipulating the authorities parameter and changing its value to ROLEADMIN, the privilege is successfully escalated to an Admin level. This allowed the access to all admin-related functionalities in the application.

Other sources

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 ROLEUSER. By manipulating the authorities parameter and changing its value to ROLEADMIN, the privilege is successfully escalated to an Admin level. This allowed the access to all admin-related functionalities in the application. NOTE: this is disputed by the Supplier because there is no privilege escalation in the context of the JHipster backend (the report only demonstrates that, after using JHipster to generate an application, one can make a non-functional admin screen visible in the front end of that application).

— NVD

Affected Software

2 affected componentsFixes available
JHipster JHipster<8.9.0
npm/generator-jhipster<8.9.0
8.9.0

Event History

Jul 25, 2025
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:15 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·03:30 PM
Data Sourced
via GitHub·03:30 PM
DescriptionSeverityWeaknessAffected Software
Aug 4, 2025
Withdrawn
via GitHub·08:26 PM

Frequently Asked Questions

1

What is the severity of CVE-2025-43712?

CVE-2025-43712 has been classified with a high severity level due to the potential for privilege escalation.

2

How do I fix CVE-2025-43712?

To fix CVE-2025-43712, upgrade to JHipster version 8.9.0 or later to ensure the authorities parameter is properly validated.

3

What systems are affected by CVE-2025-43712?

CVE-2025-43712 affects all versions of JHipster prior to 8.9.0 and related packages such as generator-jhipster.

4

What type of vulnerability is CVE-2025-43712?

CVE-2025-43712 is a privilege escalation vulnerability that allows an attacker to gain elevated permissions through manipulated API responses.

5

How can I determine if my application is vulnerable to CVE-2025-43712?

You can determine if your application is vulnerable to CVE-2025-43712 by checking if you are using JHipster version prior to 8.9.0.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203