# CVE-2026-15517: Jinher OA PlanGiveOut.aspx sql injection

> Remote attackers can exploit SQL injection in Jinher OA via the httpOID parameter to read or modify database contents.

- **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:** 13 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-g9x4-g2rg-r435

## What is CVE-2026-15517?

CVE-2026-15517 is a medium-severity SQL injection vulnerability in Jinher OA, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw has been found in Jinher OA 1.0. The affected element is an unknown function of the file /C6/JHSoft.Web.PlanSummarize/PlanGiveOut.aspx. This manipulation of the argument httpOID causes sql injection. Remote exploitation of the attack is possible. The exploit has been published and may 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-15517?


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

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

## Is CVE-2026-15517 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15517 is a medium-severity SQL injection vulnerability in Jinher OA, published on 13 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-2026-15517 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-2026-15517/ (Markdown: https://insights.sbomify.com/CVE-2026-15517/index.md)
```

## Sources

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

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