# CVE-2025-43712: Privilege escalation in JHipster

> Attackers can escalate privileges to admin by manipulating the authorities parameter in generated JHipster applications, bypassing access controls.

- **Severity:** Low 2.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jul 2025
- **Updated:** 4 Aug 2025

## What is CVE-2025-43712?

CVE-2025-43712 is a low-severity vulnerability in JHipster, published on 25 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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. 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).

Weakness: CWE-284 (Improper Access Control), CWE-451 (User Interface (UI) Misrepresentation of Critical Information)

## Which versions are affected by CVE-2025-43712?


## How do I fix CVE-2025-43712?

No fix has been published for CVE-2025-43712 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-43712 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-43712 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-43712 and fix it if it is affected.

What it is: CVE-2025-43712 is a low-severity vulnerability in JHipster, published on 25 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-43712 exists.

Affected product: JHipster. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-43712/ (Markdown: https://insights.sbomify.com/CVE-2025-43712/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-43712
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-43712
- OSV: https://osv.dev/vulnerability/CVE-2025-43712

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-43712/
Summaries are generated and may contain mistakes; the official description above is the record.