CVE-2026-11412
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 weakness has been identified in Jinher OA C6. The affected element is an unknown function of the file /C6/JHSoft.Web.ModuleCount/GetFormSn.aspx. Executing a manipulation of the argument queryID can lead to sql injection. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks. 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 at /C6/JHSoft.Web.ModuleCount/GetFormSn.aspx via the queryID parameter. Remote attackers can manipulate the queryID argument to inject malicious SQL queries. Public exploits are available and the vendor has not responded 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 installationCheck for the presence of Jinher OA C6 installation directories, IIS websites, or services running on the server. Look for directories named 'C6', 'JHSoft', or 'Jinher' in the web root or application installation folders.Affected if Jinher OA C6 is installed on the server
-
Verify vulnerable endpoint existsCheck if the file /C6/JHSoft.Web.ModuleCount/GetFormSn.aspx exists in the web application directory. Inspect the IIS configuration or web server logs for requests to this path.Affected if The GetFormSn.aspx file exists in the C6/JHSoft.Web.ModuleCount path
-
Confirm queryID parameter is acceptedReview the application's form parameters, URL parameters, or API inputs that the GetFormSn.aspx endpoint accepts. Verify that 'queryID' is a recognized parameter for this endpoint.Affected if The queryID parameter is accepted by the GetFormSn.aspx endpoint
-
Test for SQL injection vulnerabilitySend a benign test request to the endpoint with queryID parameter containing SQL syntax (such as queryID=1' OR '1'='1) and observe the application's response. Check for SQL error messages, unexpected behavior, or differences in response compared to normal requests.Affected if The application returns SQL error messages or exhibits unexpected behavior when special SQL characters are included in the queryID parameter
The environment is affected if Jinher OA C6 is installed, the GetFormSn.aspx endpoint exists, and the queryID parameter accepts unsanitized input that produces SQL errors or unusual responses when injected with SQL syntax.
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 queryID parameter, or apply input validation/sanitization. If no vendor patch is available, consider deploying a web application firewall (WAF) rule as an interim control or disabling the affected module until a fix is developed.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11412 — 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-11412 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