CVE-2026-1130
SQL Injection in Yonyou KSOA 9.0 HTTP GET Parameter
Publication date: 2026-01-19
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
Can you explain this vulnerability to me?
CVE-2026-1130 is a SQL injection vulnerability in Yonyou KSOA version 9.0, specifically in the file /worksheet/worksadd_plan.jsp. The vulnerability occurs because the application accepts an untrusted HTTP GET parameter 'id' and directly concatenates it into a SQL query without proper validation or parameterization. This allows an unauthenticated remote attacker to inject malicious SQL commands, potentially gaining unauthorized access to the database, leaking sensitive data, or manipulating data. The backend database affected is Microsoft SQL Server. Exploitation requires no login or authorization and can be done remotely. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the backend database, leakage of sensitive information, data tampering, and potentially gaining administrative control over the database server. It compromises the confidentiality, integrity, and availability of the affected system. Since no authentication is required, attackers can exploit this remotely, making the risk significant for affected environments. [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 `id` parameter in the URL `/worksheet/worksadd_plan.jsp` for SQL injection. A common method is to use sqlmap with a time-based payload to confirm the injection on Microsoft SQL Server. For example, the command: sqlmap -u "http://target/worksheet/worksadd_plan.jsp?id=1" --dbms=mssql --technique=BEUSTQ --time-sec=5 --delay=5 --batch can be used to detect the vulnerability. Additionally, monitoring for unusual HTTP GET requests with suspicious SQL payloads targeting the `id` parameter or using Google dorking with the query `inurl:worksheet/worksadd_plan.jsp` can help locate vulnerable endpoints. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing parameterized queries (prepared statements) to prevent SQL injection, enforcing strict input validation on the `id` parameter to allow only expected characters (such as 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. Since no vendor patch or fix is available, replacing the affected component with an alternative product is also suggested. [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 CVE-2026-1130 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 regulations that require safeguarding sensitive information. No direct statements about compliance impact are given. [1, 2, 3]