CVE-2026-1120
Unknown Unknown - Not Provided
SQL Injection in Yonyou KSOA 9.0 HTTP GET Parameter

Publication date: 2026-01-18

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability has been found in Yonyou KSOA 9.0. The impacted element is an unknown function of the file /worksheet/del_work.jsp of the component HTTP GET Parameter Handler. The manipulation of the argument ID leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-18
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2026-01-19
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
yonyou ksoa 9.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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
Can you explain this vulnerability to me?

CVE-2026-1120 is a SQL injection vulnerability in Yonyou KSOA 9.0, specifically in the /worksheet/del_work.jsp file. The vulnerability occurs because the application accepts an untrusted HTTP GET parameter named '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 accessing or manipulating the backend Microsoft SQL Server database. [1, 2, 3]


How can this vulnerability impact me? :

This vulnerability can lead to unauthorized database access, leakage of sensitive data, data tampering, and potentially gaining administrative control over the database server. Since no authentication is required, an attacker can remotely exploit this flaw to compromise the confidentiality, integrity, and availability of the affected system. [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 /worksheet/del_work.jsp endpoint with the HTTP GET parameter 'id' for SQL injection. A common method is to use the sqlmap tool with a command like: python sqlmap.py -u "http://<target>/worksheet/del_work.jsp?id=1*" --dbms=mssql --batch --dbs. Additionally, time-based payloads such as id=1';WAITFOR DELAY '0:0:5'-- can be used to confirm the presence of the vulnerability. Vulnerable targets can also be identified using Google dorking with queries like "inurl:worksheet/del_work.jsp" to find exposed instances. [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. [1]


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 requirements under such regulations by compromising confidentiality, integrity, and availability of sensitive data. Specific compliance implications or guidance are not detailed in the available information. [1, 2, 3]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart