Database disclosure via unsanitized id and offsnum
Published Feb 23, 2026 · Updated Feb 23, 2026
SQL injection in Jinher OA C6 20260210 allows remote authenticated users to read database data through crafted id or offsnum parameters. The OfficeSupplyTypeRight.aspx endpoint fails to sanitize these user-controlled values before database processing, enabling time-based blind inference through WAITFOR delays. A valid ASP.NET session is required, and the demonstrated proof of concept extracts the current database name through response timing rather than returning query results directly.
Summary
What happened
SQL injection in Jinher OA C6 20260210 allows remote authenticated users to read database data through crafted id or offsnum parameters. The OfficeSupplyTypeRight.aspx endpoint fails to sanitize these user-controlled values before database processing, enabling time-based blind inference through WAITFOR delays. A valid ASP.NET session is required, and the demonstrated proof of concept extracts the current database name through response timing rather than returning query results directly.
The record
- CVE
- CVE-2026-2963
- Published
- Feb 23, 2026
- Updated
- Feb 23, 2026
- Vendor
- Jinher
- Product
- OA C6
- Classifications
- CWE-89, CWE-74, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 23, 2026CVE publishedPublication date reported by the CVE source.
- Feb 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=20260210
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- OfficeSupplyTypeRight.aspx time-delay proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo