CVE-2026-1122
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 was determined in Yonyou KSOA 9.0. This impacts an unknown function of the file /worksheet/work_info.jsp of the component HTTP GET Parameter Handler. This manipulation of the argument ID causes sql injection. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized. 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-07-06
AI Q&A
2026-01-19
EPSS Evaluated
2026-07-05
NVD
CVE-2026-1122

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-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 Quick Actions

Instant insights powered by AI
Executive Summary

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]

Compliance Impact

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]

Impact Analysis

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]

Detection Guidance

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]

Mitigation Strategies

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]

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-1122. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart