CVE-2026-1123
SQL Injection in Yonyou KSOA 9.0 HTTP GET Parameter Handler
Publication date: 2026-01-18
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| yonyou | ksoa | 9.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the vulnerable URL parameter 'id' in /worksheet/work_mod.jsp for SQL injection. A practical method is to use the sqlmap tool with a command like: python sqlmap.py -u "http://<target>/worksheet/work_mod.jsp?id=1*" --dbms=mssql --batch --dbs. Additionally, Google dorking with the query inurl:worksheet/work_mod.jsp can help identify vulnerable targets. [1, 3]
Can you explain this vulnerability to me?
CVE-2026-1123 is a SQL injection vulnerability in Yonyou KSOA version 9.0, specifically in the HTTP GET parameter 'id' of the file /worksheet/work_mod.jsp. The application directly concatenates this parameter into SQL queries without proper validation or parameterization, allowing remote attackers to inject malicious SQL commands without authentication. This can lead to unauthorized database access, data leakage, and manipulation. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can allow an unauthenticated remote attacker to access, leak, or manipulate sensitive data stored in the backend Microsoft SQL Server database. It can compromise the confidentiality, integrity, and availability of the affected system, potentially leading to unauthorized administrative control over the database server and disruption of services. [1, 2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing parameterized queries (prepared statements) to prevent SQL injection, applying strict input validation on the 'id' parameter (e.g., allowing only integers), deploying a Web Application Firewall (WAF) to detect and block SQL injection attempts, and disabling detailed database error messages on the frontend to avoid information leakage. Considering replacing the affected product is also suggested since no official vendor patch is available. [1, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, since the vulnerability allows unauthorized database access, data leakage, and data tampering, it could potentially lead to violations of data protection and privacy regulations that require safeguarding sensitive information. No direct statements about compliance impact are available. [1, 2, 3]