# Withdrawn Advisory: JHipster allows privilege escalation via a modified authorities parameter

Advisory record · `GHSA-cmm8-gw4m-26cw` · Withdrawn

- **Identifiers:** `GHSA-cmm8-gw4m-26cw` · `CVE-2025-43712`
- **State:** Withdrawn
- **Severity:** CVSS 2.9 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-284](https://cwe.mitre.org/data/definitions/284.html) · [CWE-451](https://cwe.mitre.org/data/definitions/451.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) · [CWE-451](https://agentprime.io/advisories/tag/cwe-451.md)
- **Published:** 25 Jul 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

**Withdrawn.** The GitHub Advisory Database withdrew this advisory on 4 Aug 2025. The record stays here, marked withdrawn.

Published by the GitHub Advisory Database at 25 Jul 2025, 15:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `generator-jhipster` (npm): affected `<8.9.0`; fixed in `8.9.0`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 2.9 Low, CVSS 3.1: `CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`, from CNA (mitre)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0030, the 22nd percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 25 Jul 2025. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-cmm8-gw4m-26cw](https://github.com/advisories/GHSA-cmm8-gw4m-26cw)
- [OSV: GHSA-cmm8-gw4m-26cw](https://osv.dev/vulnerability/GHSA-cmm8-gw4m-26cw)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-43712>
- <https://firecompass.com/cve-2025-43712-jhipster-platform-privilege-escalation-vulnerability-discovered-by-firecompass-research-added-to-nist>
- <https://github.com/jhipster/generator-jhipster>
- <https://github.com/jhipster/generator-jhipster/releases>
- <https://groups.google.com/g/jhipster-dev/c/ATSlWkEjw2w>
- <https://medium.com/@hritikgodara/cve-2025-43712-privilege-escalation-via-response-manipulation-in-the-jhipster-platform-5e18c0434def>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-cmm8-gw4m-26cw>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-cmm8-gw4m-26cw/>. Everything for agents: <https://agentprime.io/llms.txt>.