CVE-2026-15517
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSQL injection vulnerability in Jinher OA 1.0 at /C6/JHSoft.Web.PlanSummarize/PlanGiveOut.aspx via the httpOID parameter. The application fails to properly sanitize user input before using it in SQL queries, allowing remote attackers to inject malicious SQL statements. A public exploit exists, increasing urgency.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Jinher OA 1.0 installationCheck web server logs, installed applications, or scan for the Jinher OA web interface. Common paths may include /C6/ orJHSoft/ directories. Inspect HTTP responses for 'JHSoft' or 'Jinher' strings in headers or page content.Affected if Jinher OA 1.0 is installed and accessible on the network
-
Verify vulnerable endpoint existsSend an HTTP GET request to /C6/JHSoft.Web.PlanSummarize/PlanGiveOut.aspx. Check if the page loads or returns a valid HTTP response (200 or similar).Affected if The endpoint returns a valid response, indicating the vulnerable component is present
-
Confirm httpOID parameter acceptanceSend a POST or GET request to PlanGiveOut.aspx with an httpOID parameter (e.g., httpOID=1). Observe if the application processes the parameter without error or returns different content based on the value.Affected if The application accepts and processes the httpOID parameter without sanitization errors
-
Check for SQL injection indicatorsReview application logs, database logs, or WAF logs for suspicious SQL patterns in httpOID parameter values. Look for SQL error messages in application responses that may reveal SQL injection vulnerability.Affected if SQL syntax errors, unexpected database responses, or injection patterns appear in logs or responses
-
Scan for public exploit artifactsCheck for presence of exploit tools or scripts targeting CVE-2026-15517 in network traffic logs, endpoint monitoring, or intrusion detection alerts. Look for outbound connections to known exploit repositories.Affected if Exploit tools or related attack traffic targeting this CVE is detected
The environment is affected if Jinher OA 1.0 is installed and the /C6/JHSoft.Web.PlanSummarize/PlanGiveOut.aspx endpoint is accessible with the httpOID parameter functional.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement parameterized queries or prepared statements for the httpOID parameter. As an interim measure, deploy a WAF rule to block SQL injection patterns. Since the vendor did not respond, consider third-party security support or alternative OA solutions if no patch is available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15517 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-15517 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data