# CVE-2025-60931: Missing authorization in n/a

> Unauthorized attackers can view other employees' compensation data via crafted requests in Infor Global HR.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** GHSA-vh3g-j958-pvhc

## What is CVE-2025-60931?

CVE-2025-60931 is a high-severity missing authorization vulnerability in n/a, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Insecure Direct Object Reference (IDOR) in the Employee Compensation View function of Infor Global HR v11.24.10.01.33 allows unauthorized attackers to arbitrarily view the compensation information of other employees via a crafted GET request.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2025-60931 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60931 is a high-severity missing authorization vulnerability in n/a, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60931 exists.

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

## Sources

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

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