CVE-2026-2963
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 vulnerability was determined in Jinher OA C6 up to 20260210. This issue affects some unknown processing of the file /C6/Jhsoft.Web.officesupply/OfficeSupplyTypeRight.aspx. This manipulation of the argument id/offsnum causes sql injection. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized. It is suggested to install a patch to address this issue. 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 C6 (up to 20260210) in the OfficeSupplyTypeRight.aspx file allows remote attackers to inject malicious SQL queries through the id/offsnum parameters. The exploit is publicly available and the vendor failed to respond to disclosure.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 C6 installationLocate the Jinher OA C6 application installation directory. Common paths include C:\Jinher\OA\ or C:\Program Files\Jinher\OAC6\. Check for the presence of OA system files and the OfficeSupplyTypeRight.aspx file within the web root.Affected if Jinher OA C6 is installed and the OfficeSupplyTypeRight.aspx file exists in the web application directory.
-
Check installed version against affected rangeExamine version information files (such as version.txt, info.config, or the assembly version in bin files) within the Jinher OA installation directory. Compare the build version to 20260210.Affected if The installed version is 20260210 or earlier.
-
Verify vulnerable endpoint exists and is accessibleLocate OfficeSupplyTypeRight.aspx in the web application's directory structure. This file is typically found under the OA web root, often in a module subfolder related to office supply management.Affected if The OfficeSupplyTypeRight.aspx file is present and the web server serves this endpoint.
-
Inspect parameter handling in the affected fileExamine the code-behind file (OfficeSupplyTypeRight.aspx.cs or similar) for the id and offsnum parameters. Look for direct string concatenation or unsanitized use of these request parameters in SQL queries.Affected if The code directly incorporates id or offsnum parameters into SQL queries without parameterized queries or input sanitization.
A user is affected if Jinher OA C6 is installed with version 20260210 or earlier, the OfficeSupplyTypeRight.aspx file exists, and the application accepts user input through the id or offsnum parameters in an unsafe manner.
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 stored procedures for all database interactions in the affected file. Until a vendor patch is available, consider deploying a WAF rule to block SQL injection payloads or temporarily disable the affected endpoint if not business-critical.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2963 — 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-2963 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