CVE-2025-15436
SQL Injection in Yonyou KSOA 9.0 /worksheet/work_edit.jsp
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 | 1.0 |
| yonyou | ksoa | 9.0 |
Helpful Resources
Exploitability
| 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-2025-15436 is a SQL injection vulnerability in Yonyou KSOA 9.0, specifically in the /worksheet/work_edit.jsp file. The vulnerability occurs because the application does not properly sanitize or validate the 'Report' parameter, which can be manipulated remotely without authentication. Attackers can inject malicious SQL code through this parameter, allowing them to alter SQL queries and perform unauthorized database operations. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, leakage of sensitive data, data tampering, full system control by attackers, and potential service interruptions. Since it can be exploited remotely without authentication, it poses significant risks to system security and business continuity. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'Report' parameter in the URL /worksheet/work_edit.jsp for SQL injection. One suggested command is using sqlmap to automate detection: python sqlmap.py --random-agent --batch -u "http://<target-ip>:<port>/worksheet/work_edit.jsp?Report=12211". Additionally, a proof-of-concept payload such as Report=12211';WAITFOR DELAY '0:0:5'-- can be used to check for time-based SQL injection delays. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Using prepared statements and parameter binding to separate SQL code from user input, preventing injection; 2) Implementing strict input validation and filtering to ensure inputs conform to expected formats (e.g., numeric patterns for IDs); 3) Minimizing database user permissions by avoiding high-privilege accounts for routine operations; 4) Conducting regular security audits to detect and address vulnerabilities promptly. Since no authentication is required to exploit this vulnerability, these measures are critical to protect data integrity and system security. [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized access, data leakage, and data tampering due to SQL injection, which can compromise the confidentiality, integrity, and availability of sensitive data. Such security breaches can lead to non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive information. Failure to remediate this vulnerability may result in violations of these regulations due to unauthorized data exposure and lack of adequate security controls. [1, 2]