CVE-2026-1124
SQL Injection in Yonyou KSOA 9.0 /worksheet/work_report.jsp
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
Can you explain this vulnerability to me?
CVE-2026-1124 is a SQL injection vulnerability in Yonyou KSOA 9.0, specifically in the file /worksheet/work_report.jsp. The vulnerability occurs because the application takes an HTTP GET parameter 'id' and directly inserts it into a SQL query without proper validation or parameterization. This allows an unauthenticated remote attacker to inject malicious SQL commands, potentially accessing or manipulating the backend Microsoft SQL Server database. The flaw arises from improper handling of user input, enabling attackers to execute unauthorized SQL queries. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, leakage of sensitive data, data tampering, and potentially gaining administrative control over the database server. Since no authentication is required, attackers can remotely exploit this flaw to compromise the confidentiality, integrity, and availability of the affected system. This can result in significant security breaches and operational disruptions. [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 HTTP GET parameter 'id' in the URL /worksheet/work_report.jsp for SQL injection. A common detection method is to send a payload that causes a time delay, such as: id=1';WAITFOR DELAY '0:0:5'--. If the response is delayed by about 5 seconds, it indicates a SQL injection vulnerability. Additionally, vulnerable targets can be identified using Google dorking with the query: inurl:worksheet/work_report.jsp. Network or web application firewall logs can also be monitored for suspicious requests containing SQL injection patterns targeting the 'id' parameter. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements (parameterized queries) to ensure user input is treated as data, not executable code. 2) Apply strict input validation on the 'id' parameter, allowing only expected characters such as integers. 3) Deploy a Web Application Firewall (WAF) to detect and block SQL injection attempts. 4) Disable detailed database error messages on the frontend to prevent information leakage. If possible, replace the affected component with an alternative product to avoid exploitation, as the vendor has not provided any patches or countermeasures. [1, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not contain information regarding the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.