VulnerabilityPublished 2 Jan 2026Updated 23 Feb 2026

CVE-2025-15434: Yonyou KSOA · SQL Injection

Affects Yonyou KSOASource CVE Database V5

Public exploit available · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Yonyou KSOA	Affected =9.0	Fixed in–

AI-suggested

Implement strict input validation and sanitization on all user-supplied parameters, especially 'zpjhid', to prevent malicious SQL code injection.
Deploy a Web Application Firewall (WAF) with rules tailored to detect and block SQL injection attempts targeting the /kp/PrintZPYG.jsp endpoint.
Conduct thorough code reviews and security testing of the affected application components to identify and remediate injection flaws.
Monitor application logs and network traffic for unusual or suspicious requests indicative of exploitation attempts.
Restrict network access to the vulnerable application to trusted IP addresses where feasible, reducing exposure.
Isolate the database with least privilege principles, ensuring the application account has minimal permissions to limit damage if exploited.
Engage with Yonyou support channels persistently to obtain official patches or guidance.
Prepare incident response plans for potential exploitation scenarios, including data breach containment and forensic analysis.
Consider temporary application-layer proxies or API gateways that can sanitize inputs or block malicious payloads until a patch is available.
Educate relevant IT and security staff about this vulnerability and the importance of rapid mitigation.

Description

A vulnerability was detected in Yonyou KSOA 9.0. Affected is an unknown function of the file /kp/PrintZPYG.jsp. The manipulation of the argument zpjhid results in sql injection. It is possible to launch the attack remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The impact of CVE-2025-15434 is significant for organizations using Yonyou KSOA 9.0, as successful exploitation can lead to unauthorized access to sensitive enterprise data stored in backend databases. This includes potential exposure of confidential business information, customer data, and internal operational details. Attackers could also modify or delete critical data, undermining data integrity and disrupting business processes. Since the vulnerability requires no authentication and can be exploited remotely, it broadens the attack surface considerably. The availability of a public exploit increases the likelihood of opportunistic attacks and automated scanning. Organizations without adequate protections may face data breaches, regulatory penalties, reputational damage, and operational downtime. The lack of vendor response and patch availability exacerbates the risk, forcing organizations to rely on interim mitigations. Given Yonyou's strong market presence in China and parts of Asia, enterprises in these regions are particularly vulnerable. The threat could also extend to international companies using Yonyou KSOA in their supply chains or subsidiaries.

Summary

CVE-2025-15434 identifies a SQL injection vulnerability in Yonyou KSOA version 9.0, specifically within the /kp/PrintZPYG.jsp endpoint. The vulnerability arises from improper sanitization of the 'zpjhid' parameter, allowing attackers to inject malicious SQL code. Exploiting this flaw enables remote attackers to execute arbitrary SQL commands on the backend database without requiring authentication or user interaction. This can lead to unauthorized data disclosure, data modification, or potentially full compromise of the affected database. The vulnerability has a CVSS 4.0 base score of 6.9, reflecting medium severity due to the lack of authentication and ease of exploitation, but limited scope and impact on confidentiality, integrity, and availability. Public exploit code has been released, increasing the risk of exploitation by threat actors. The vulnerability affects only version 9.0 of KSOA, a widely used enterprise application suite, particularly in China and other Asian markets. The attack vector is network-based, requiring only the ability to send crafted HTTP requests to the vulnerable endpoint. Given the nature of SQL injection, attackers could potentially extract sensitive data, alter records, or disrupt application functionality. Organizations relying on Yonyou KSOA 9.0 should urgently assess exposure and implement compensating controls to mitigate risk until a patch is available.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 23:03 UTC

Technical details

References

Community reviews

Related threats