# CVE-2025-59714: Missing authorization in Grouper

> Group admins can improperly configure loader jobs, allowing unauthorized modification of system configurations.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2025
- **Updated:** 19 Sep 2025
- **Also known as:** GHSA-9w3p-67mx-gphr

## What is CVE-2025-59714?

CVE-2025-59714 is a medium-severity missing authorization vulnerability in Internet2 Grouper, published on 19 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In Internet2 Grouper 5.17.1 before 5.20.5, group admins who are not Grouper sysadmins can configure loader jobs.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Internet2 Grouper.

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

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

## Is CVE-2025-59714 being exploited?

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

## Other vulnerabilities in Internet2 Grouper

- [CVE-2018-19794](https://insights.sbomify.com/CVE-2018-19794/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59714 is a medium-severity missing authorization vulnerability in Internet2 Grouper, published on 19 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59714 exists.

Affected product: Internet2 Grouper. 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-59714/ (Markdown: https://insights.sbomify.com/CVE-2025-59714/index.md)
```

## Sources

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

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