CVE-2025-15420VulnerabilityPublished 2 Jan 2026Updated 23 Feb 2026

CVE-2025-15420: Yonyou KSOA · SQL Injection

Affects Yonyou KSOASource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 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 39% 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: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

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 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

Organizations should immediately conduct an inventory to identify any deployments of Yonyou KSOA version 9.0. Until a vendor patch is available, implement strict network-level access controls to restrict access to the affected application, especially the /worksheet/agent_work_report.jsp endpoint. Employ web application firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the ID parameter. Conduct thorough input validation and sanitization on all user-supplied data within the application if source code access and modification are possible. Monitor logs for suspicious activity indicative of SQL injection attempts. Consider deploying database activity monitoring to detect anomalous queries. Engage with Yonyou support channels for updates and patches. Plan for rapid patch deployment once available. Additionally, conduct regular backups of critical data and test restoration procedures to mitigate potential data loss. Educate development and security teams about secure coding practices to prevent similar vulnerabilities in future releases.

Description

A security vulnerability has been detected in Yonyou KSOA 9.0. This affects an unknown part of the file /worksheet/agent_work_report.jsp. The manipulation of the argument ID leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The SQL injection vulnerability in Yonyou KSOA 9.0 poses significant risks to organizations relying on this software for business process automation. Successful exploitation can lead to unauthorized disclosure of sensitive business data, including financial records, employee information, and operational details. Attackers could alter or delete data, undermining data integrity and potentially causing operational disruptions. Since the vulnerability can be exploited remotely without authentication, it increases the attack surface and risk of automated attacks or mass exploitation campaigns. The lack of vendor response and patches prolongs exposure, increasing the window for attackers to develop and deploy exploits. Organizations in sectors such as finance, manufacturing, government, and large enterprises using Yonyou KSOA are particularly vulnerable. The compromise of ERP systems can also facilitate lateral movement within networks, leading to broader organizational impact. Overall, the vulnerability threatens confidentiality, integrity, and availability of critical business systems and data.

Summary

CVE-2025-15420 is a SQL injection vulnerability identified in Yonyou KSOA version 9.0, a widely used enterprise resource planning (ERP) and office automation software suite. The vulnerability exists in the /worksheet/agent_work_report.jsp file, where the ID parameter is improperly sanitized, allowing attackers to inject malicious SQL commands. This injection flaw can be exploited remotely without authentication or user interaction, enabling attackers to manipulate backend database queries. Potential consequences include unauthorized data access, data modification, or deletion, and possibly further compromise of the underlying system. The vulnerability has been publicly disclosed, and exploit code is available, although no known widespread exploitation has been reported to date. The vendor has not responded to notifications, and no official patches have been released, leaving affected systems exposed. The CVSS 4.0 base score is 6.9, reflecting a medium severity level due to the ease of exploitation and potential impact on confidentiality, integrity, and availability. The vulnerability affects only version 9.0 of Yonyou KSOA, and no other versions have been reported as vulnerable. Given the critical role of ERP systems in business operations, exploitation could disrupt workflows and compromise sensitive corporate data.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 22:59 UTC

Technical details

References

Community reviews

Related threats