CVE-2026-1122
SQL Injection in Yonyou KSOA 9.0 HTTP GET Parameter
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-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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This SQL injection vulnerability compromises the confidentiality, integrity, and availability of the affected system, potentially leading to unauthorized access and leakage of sensitive data. Such impacts can result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and breaches. Therefore, exploitation of this vulnerability could lead to violations of these standards due to data exposure and insufficient security controls. [1, 2]
Can you explain this vulnerability to me?
CVE-2026-1122 is a SQL injection vulnerability in Yonyou KSOA version 9.0, specifically in the file /worksheet/work_info.jsp. The vulnerability occurs because the HTTP GET parameter 'id' is not properly validated or neutralized before being used in a SQL query. This allows an attacker to inject malicious SQL code remotely without authentication, potentially compromising the system's confidentiality, integrity, and availability. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can allow an unauthenticated remote attacker to execute arbitrary SQL commands on the backend database, leading to unauthorized access to sensitive data, data leakage, data tampering, and potentially administrative control over the database server. It compromises confidentiality, integrity, and availability of the affected system, posing a severe security risk. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the affected URL parameter for SQL injection. One suggested method is using the sqlmap tool to test the 'id' parameter in the URL '/worksheet/work_info.jsp'. For example, the command: `python sqlmap.py -u "http://<target>/worksheet/work_info.jsp?id=1*" --dbms=mssql --batch --dbs` can be used to detect the vulnerability. Additionally, a time-based payload such as `http://<target>/worksheet/work_info.jsp?id=1';WAITFOR DELAY '0:0:5'--` can be used to confirm SQL injection by observing response delays. Attackers may also use Google dorking with the query `inurl:worksheet/work_info.jsp` to identify potentially vulnerable targets. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameterized queries to prevent SQL injection by treating user input strictly as data; 2) Enforcing strict input validation on the 'id' parameter, allowing only expected characters such as integers; 3) Deploying a Web Application Firewall (WAF) to detect and block common SQL injection patterns; 4) Disabling detailed database error messages on the frontend to avoid information leakage. Additionally, replacing the affected component with an alternative product is suggested since no vendor patch is available. [1, 2]