CVE-2026-1131
SQL Injection in Yonyou KSOA 9.0 HTTP Parameter Handler
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-1131 is a SQL injection vulnerability in Yonyou KSOA Platform version 9.0. It exists in the /kmc/save_catalog.jsp file, specifically in the handling of the HTTP GET parameter 'catalogid'. The application directly concatenates this parameter into a SQL query without proper validation or parameterization, allowing an unauthenticated remote attacker to inject arbitrary SQL commands. This can lead to unauthorized access to the backend Microsoft SQL Server database, data leakage, data tampering, or even administrative control over the database server. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized database access, leakage of sensitive data, manipulation or tampering of data, and potentially gaining administrative control over the database server. Since no authentication is required to exploit it, attackers can remotely execute arbitrary SQL commands, compromising 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 sending specially crafted HTTP GET requests to the vulnerable endpoint `/kmc/save_catalog.jsp` with the `catalogid` parameter containing SQL injection payloads. For example, a time-based SQL injection test can be performed using a command like: `curl "http://<target>/kmc/save_catalog.jsp?catalogid=1';WAITFOR DELAY '0:0:5'--"` which induces a delay if the injection is successful. Additionally, Google dorking can be used to identify potentially vulnerable targets by searching for `inurl:kmc/save_catalog.jsp`. Deploying a Web Application Firewall (WAF) can also help detect and block such SQL injection attempts. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement parameterized queries (Prepared Statements) to prevent SQL injection by treating user input as data, not executable code. 2) Apply strict input validation on the `catalogid` parameter, restricting it to expected formats such as integers only. 3) Deploy a Web Application Firewall (WAF) to detect and block SQL injection attempts. 4) Disable detailed database error messages on the frontend to avoid information leakage. Since no patches or vendor responses are available, consider replacing the affected component with an alternative product if possible. [2, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This SQL injection vulnerability allows unauthorized remote attackers to access, leak, and manipulate sensitive data in the affected system without authentication. Such unauthorized access and data leakage can lead to 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 result in violations of these standards due to compromised confidentiality, integrity, and availability of protected data. [1, 2, 3]