CVE-2026-1123
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 identified in Yonyou KSOA 9.0. Affected is an unknown function of the file /worksheet/work_mod.jsp of the component HTTP GET Parameter Handler. Such manipulation of the argument ID leads to sql injection. The attack may be launched remotely. The exploit is publicly available and might 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 · high confidenceYonyou KSOA 9.0 contains a SQL injection vulnerability in the /worksheet/work_mod.jsp file via the ID GET parameter. An unauthenticated remote attacker can exploit this to inject arbitrary SQL commands, potentially leading to full database compromise, data exfiltration, or remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 9.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify if Yonyou KSOA is installedSearch for Yonyou KSOA installation directories or check for the 'ksoa' product name in installed software inventoriesAffected if Yonyou KSOA software is present on the system
-
Confirm the installed version is 9.0Locate version information in the KSOA installation - check installation directories, About pages, or version files typically found in the product's root or system directoriesAffected if The installed version is exactly 9.0
-
Locate the vulnerable JSP fileSearch for the file /worksheet/work_mod.jsp within the KSOA web application directory structure - this is typically under the webroot or htdocs folder of the installationAffected if The file /worksheet/work_mod.jsp exists in the KSOA web directory
-
Verify the vulnerable endpoint is accessibleTest if HTTP access to /worksheet/work_mod.jsp returns a valid response - check if the application is serving this endpoint via HTTP/HTTPSAffected if The endpoint /worksheet/work_mod.jsp is reachable over the network
You are affected if Yonyou KSOA version 9.0 is installed AND the /worksheet/work_mod.jsp file is present and accessible, as this specific version contains the SQL injection flaw in the ID parameter handler.
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 dataSince the vendor did not respond, apply compensatory controls: disable or restrict access to the vulnerable /worksheet/work_mod.jsp endpoint via web server configuration or WAF rules, implement strict input validation on the ID parameter, and consider network segmentation to limit exposure to untrusted networks.
- 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-1123 — 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-1123 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