CVE-2026-1129
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 detected in Yonyou KSOA 9.0. This vulnerability affects unknown code of the file /worksheet/worksadd.jsp of the component HTTP GET Parameter Handler. The manipulation of the argument ID results in sql injection. The attack may be performed from remote. The exploit is now public 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 · high confidenceSQL injection vulnerability in Yonyou KSOA 9.0 allows remote attackers to inject malicious SQL queries via the ID parameter in the /worksheet/worksadd.jsp file. The vulnerability is actively exploited and requires no authentication, enabling complete database compromise.
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 Yonyou KSOA installation and versionCheck for the presence of Yonyou KSOA web application files in the web server root directory or check the application's About/Version page. Common paths include /ksoa or /KSOA directories. Look for version information in the application metadata or startup logs.Affected if The installed version is Yonyou KSOA version 9.0 exactly
-
Verify worksadd.jsp is accessibleAttempt to access the vulnerable endpoint via HTTP GET request to /worksheet/worksadd.jsp on the server. Check if the application returns a valid response rather than a 404 error.Affected if The /worksheet/worksadd.jsp endpoint exists and responds to HTTP requests
-
Confirm the ID parameter is acceptedSend a benign HTTP GET request to /worksheet/worksadd.jsp with a test ID parameter value (e.g., ?ID=1) and observe the application's response to confirm the parameter is processed.Affected if The ID parameter is accepted and processed by the worksadd.jsp page without validation errors
-
Test for SQL injection behaviorCompare application responses when sending a valid ID value versus a SQL injection payload (e.g., ID=1' OR '1'='1). Look for differences in database error messages, response content, or application behavior that indicate unsanitized SQL input.Affected if The application exhibits different behavior when SQL syntax is injected into the ID parameter, suggesting the input is not properly sanitized before being used in a database query
You are affected if Yonyou KSOA version 9.0 is running and the /worksheet/worksadd.jsp endpoint is accessible with an unpatched ID parameter vulnerable to SQL injection.
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 dataImmediately restrict network access to the /worksheet/worksadd.jsp endpoint and implement WAF rules to block SQL injection patterns. Until vendor patch is available, consider disabling the affected functionality or implementing compensating controls.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1129 — 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-1129 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