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

> Attackers can access sensitive user information via a crafted GET request due to incorrect access control in the jshERP user info interface.

- **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:** 28 Oct 2025
- **Updated:** 29 Oct 2025
- **Also known as:** GHSA-q7fw-jpjh-xmmm

## What is CVE-2025-60800?

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

### Official description

Incorrect access control in the /jshERP-boot/user/info interface of jshERP up to commit 90c411a allows attackers to access sensitive information via a crafted GET request.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Jishenghua Jsherp.

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

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

## Is CVE-2025-60800 being exploited?

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

Public exploit code:

- VulDB advisory: jshERP authenticated /user/info IDOR and password-digest replay after CVE-2025-60800 (github_poc): https://github.com/Bob-wentao/jsherp-user-info-idor

## Other vulnerabilities in n/a

- [CVE-2025-51742](https://insights.sbomify.com/CVE-2025-51742/): Deserialization in n/a (critical 9.8)
- [CVE-2025-51743](https://insights.sbomify.com/CVE-2025-51743/): Deserialization in n/a (critical 9.8)
- [CVE-2025-51744](https://insights.sbomify.com/CVE-2025-51744/): Deserialization in n/a (critical 9.8)
- [CVE-2025-51745](https://insights.sbomify.com/CVE-2025-51745/): Deserialization in n/a (critical 9.8)
- [CVE-2025-51746](https://insights.sbomify.com/CVE-2025-51746/): Deserialization in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60800 is a high-severity missing authorization vulnerability in n/a, published on 28 Oct 2025. 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-60800 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-60800/ (Markdown: https://insights.sbomify.com/CVE-2025-60800/index.md)
```

## Sources

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

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