CVE-2026-7670
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/UserSel.aspx. This manipulation of the argument DeptIDList causes sql injection. The attack is possible to be carried out remotely. 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 allows remote attackers to inject malicious SQL queries via the DeptIDList parameter in the /C6/JHSoft.Web.PlanSummarize/UserSel.aspx endpoint. The vulnerability is remotely exploitable and public exploits are available.
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 is deployedIdentify if Jinher OA application is running in your environment by checking web server logs, installed applications, or by accessing the application URLAffected if Jinher OA 1.0 is present in the environment
-
Verify vulnerable endpoint existsCheck if the URL /C6/JHSoft.Web.PlanSummarize/UserSel.aspx is accessible in your Jinher OA installation by attempting to access it or reviewing web server configurationAffected if The endpoint /C6/JHSoft.Web.PlanSummarize/UserSel.aspx is present and reachable
-
Inspect DeptIDList parameter handlingReview the code or decompile the assembly handling the UserSel.aspx page to determine if the DeptIDList parameter is used directly in SQL queries without parameterized queries or prepared statementsAffected if The DeptIDList parameter is processed using dynamic SQL concatenation without parameterized queries
-
Check for SQL injection indicators in logsReview web application and database logs for unusual or malformed queries involving the DeptIDList parameter that may indicate exploitation attemptsAffected if Logs show unexpected SQL syntax or multiple failed queries targeting the DeptIDList parameter
You are affected if Jinher OA 1.0 is running and the /C6/JHSoft.Web.PlanSummarize/UserSel.aspx endpoint exists with the DeptIDList parameter being processed via dynamic SQL rather than parameterized queries.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements for the DeptIDList parameter and implement proper input validation. Apply input sanitization as an additional defense layer until the code fix is deployed.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7670 — 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-7670 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