CVE-2025-15447
SQL Injection in Seeyon Zhiyuan OA Remote Exploit
Publication date: 2026-01-05
Last updated on: 2026-01-05
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| seeyon | zhiyuan_oa_web_application_system | to 20251223 (inc) |
| seeyon | collaborative_platform | 1.0 |
| seeyon | seeyou_collaborative_platform | 1.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-2025-15447 is a critical SQL injection vulnerability in the Seeyon Zhiyuan OA Web Application System, specifically in the file /assetsGroupReport/assetsService.jsp. The vulnerability occurs because the application does not properly sanitize or validate the 'unitCode' parameter, allowing attackers to inject malicious SQL code remotely without authentication. This enables attackers to manipulate database queries, potentially accessing or altering sensitive data and compromising the system. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive information, data tampering, full system control by attackers, and potential disruption of services. Since no authentication is required to exploit it, the risk is significantly high, threatening 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 vulnerable endpoint /assetsGroupReport/assetsService.jsp with specially crafted payloads targeting the 'unitCode' parameter to check for SQL injection. For example, sending a POST request with payloads like `unitCode=11';WAITFOR DELAY '0:0:5'--` can cause a delayed response if the injection is successful. Automated tools such as sqlmap can be used to scan and confirm the vulnerability by targeting the 'unitCode' parameter on the affected URL. Example sqlmap command: `sqlmap -u "http://target/assetsGroupReport/assetsService.jsp" --data="unitCode=11" -p unitCode --technique=BEUSTQ --dbms=Microsoft SQL Server`. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements and parameterized queries to separate SQL code from user input, preventing injection. 2) Applying strict input validation and filtering on the 'unitCode' parameter to ensure only expected formats are accepted. 3) Minimizing database user permissions by avoiding use of high-privilege accounts for routine database operations. 4) Conducting regular security audits to detect and remediate vulnerabilities promptly. Since no official patch or vendor response is available, consider replacing the affected component or disabling the vulnerable functionality until a fix is available. [1, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows unauthorized access, data leakage, and data tampering due to SQL injection, which can lead to breaches of confidentiality, integrity, and availability of sensitive data. Such impacts can result in non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive information. Therefore, exploitation of this vulnerability poses a significant risk to compliance with these regulations. [1, 2]