CVE-2025-15424
SQL Injection in Yonyou KSOA 9.0 HTTP GET Parameter Handler
Publication date: 2026-01-02
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?
This vulnerability is a SQL injection flaw in Yonyou KSOA version 9.0, specifically in the file /worksheet/agent_worksdel.jsp. The application accepts an 'id' parameter via an HTTP GET request, which is directly concatenated into a backend SQL query without proper input validation or parameterization. This allows an unauthenticated remote attacker to inject malicious SQL commands, potentially manipulating the database. [1, 2, 4]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, and manipulation of the server. Since the attack can be performed remotely without authentication, it poses a high risk of compromising the confidentiality, integrity, and availability of the affected system. [1, 2, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the vulnerable endpoint `/worksheet/agent_worksdel.jsp` that accepts an `id` parameter via HTTP GET requests. Attackers may use techniques such as Google dorking with queries like `inurl:worksheet/agent_worksdel.jsp` to locate vulnerable targets. To detect exploitation attempts on your system, you can monitor HTTP GET requests to this endpoint and look for suspicious or malformed `id` parameter values that may contain SQL injection payloads. For example, you can use tools like curl or wget to test the endpoint manually, or use network monitoring tools to capture and analyze traffic. Example command to test the endpoint for SQL injection: `curl -v "http://<target>/worksheet/agent_worksdel.jsp?id=1' OR '1'='1"` and observe if the response indicates SQL errors or unexpected behavior. Additionally, monitoring web server logs for unusual query strings or error messages related to SQL syntax can help detect exploitation attempts. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or restricting access to the vulnerable endpoint `/worksheet/agent_worksdel.jsp` if possible. Since no vendor patches or countermeasures are available and the vendor did not respond, it is recommended to replace the affected component with an alternative product or version that is not vulnerable. Additionally, implementing web application firewall (WAF) rules to block malicious SQL injection payloads targeting the `id` parameter can help reduce risk. Monitoring and blocking suspicious traffic patterns and applying strict input validation or parameterized queries in the application code (if you have control over it) are also advisable. Ultimately, removing or isolating the vulnerable service until a secure fix is available is the safest approach. [2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not specify how this SQL injection vulnerability in Yonyou KSOA 9.0 affects compliance with common standards and regulations such as GDPR or HIPAA. However, since the vulnerability allows unauthorized database access and potential data leakage, it could lead to non-compliance with data protection regulations that require safeguarding sensitive information. No explicit details or analysis regarding compliance impact are given in the resources. [1, 2, 4]