# CVE-2026-124331: Jinher OA ProjectAfficheManage.aspx sql injection


- **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
- **Fix available:** No
- **Published:** 8 Nov 2026
- **Updated:** 8 Nov 2026
- **Also known as:** GHSA-xh95-44r3-wvvp

## What is CVE-2026-124331?

CVE-2026-124331 is a medium-severity vulnerability in Jinher OA, published on 8 Nov 2026. 

### Official description

A vulnerability was identified in Jinher OA C6. This impacts an unknown function of the file /C6/JHSoft.Web.Project/OfficeReadOnly/ProjectAfficheManage.aspx. Such manipulation of the argument ProjID leads to sql injection. It is possible to launch the attack remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-124331?


## How do I fix CVE-2026-124331?

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

## Is CVE-2026-124331 being exploited?

There is no known exploitation of CVE-2026-124331 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-124331 and fix it if it is affected.

What it is: CVE-2026-124331 is a medium-severity vulnerability in Jinher OA, published on 8 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124331 in the wild and no public exploit code.

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-2026-124331/ (Markdown: https://insights.sbomify.com/CVE-2026-124331/index.md)
```

## Sources

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

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