# CVE-2025-7823: Jinher OA ProjectScheduleDelete.aspx xml external entity reference

> Remote attackers can exploit an XML External Entity vulnerability in Jinher OA to read sensitive data or cause denial of service.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jul 2025
- **Updated:** 21 Jul 2025
- **Also known as:** GHSA-7hcv-42fj-r6vq

## What is CVE-2025-7823?

CVE-2025-7823 is a medium-severity vulnerability in Jinher OA, published on 19 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in Jinher OA 1.2. It has been declared as problematic. This vulnerability affects unknown code of the file ProjectScheduleDelete.aspx. The manipulation leads to xml external entity reference. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference), CWE-610 (Externally Controlled Reference to a Resource in Another Sphere)

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

It affects 1 product.


Products: Jinher Jinher Oa.

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

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

## Is CVE-2025-7823 being exploited?

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

## Other vulnerabilities in Jinher OA

- [CVE-2025-11341](https://insights.sbomify.com/CVE-2025-11341/): Jinher OA type xml external entity reference (medium 6.9)
- [CVE-2025-10816](https://insights.sbomify.com/CVE-2025-10816/): Jinher OA XML text xml external entity reference (medium 6.9)
- [CVE-2025-10090](https://insights.sbomify.com/CVE-2025-10090/): Jinher OA GetTreeDate.aspx sql injection (medium 6.9)
- [CVE-2025-10091](https://insights.sbomify.com/CVE-2025-10091/): Jinher OA XML Type xml external entity reference (medium 6.9)
- [CVE-2025-10092](https://insights.sbomify.com/CVE-2025-10092/): Jinher OA XML Type xml external entity reference (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7823 is a medium-severity vulnerability in Jinher OA, published on 19 Jul 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-7823 exists.

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

## Sources

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

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