CVE-2025-15434
SQL Injection in Yonyou KSOA 9.0 /kp/PrintZPYG.jsp Allows Remote Attack
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-15434 is a SQL injection vulnerability in Yonyou KSOA version 9.0, specifically in the /kp/PrintZPYG.jsp file. The vulnerability occurs because the application does not properly sanitize or validate the 'zpjhid' parameter before using it in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially manipulating database queries to access or alter data unauthorizedly. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, leakage of sensitive data, data tampering, full system control, and disruption of services. Attackers can execute arbitrary SQL commands remotely without authentication, which poses severe risks to system security and business continuity. [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 vulnerable parameter 'zpjhid' in the URL '/kp/PrintZPYG.jsp' for SQL injection. One practical method is to use sqlmap with a command like: python sqlmap.py --random-agent --batch -u "http://<target-ip>:<port>/kp/PrintZPYG.jsp?zpjhid=1" --current-db. Additionally, attackers or testers can use Google dorking with the query 'inurl:kp/PrintZPYG.jsp' to identify potentially vulnerable targets. Testing can include injecting payloads such as '1';WAITFOR DELAY '0:0:5'--' to check for time delays indicating SQL injection. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, enforcing strict input validation and filtering (e.g., allowing only numeric patterns for the 'zpjhid' parameter), and minimizing database user permissions by avoiding high-privilege accounts for routine operations. Regular security audits should be conducted to detect and remediate vulnerabilities promptly. Since the vendor has not provided patches or mitigations, consider replacing the affected component with an alternative product to reduce risk. [2, 3]
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 SQL injection vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, given that the vulnerability allows unauthorized database access, data leakage, and data tampering, it could potentially lead to non-compliance with data protection regulations that require safeguarding sensitive data. No direct statements or analyses regarding compliance impact are available in the provided texts. [2, 3]