Cyber Resilience

CVE-2025-15425

SQLi in Yonyou Ksoa 9.0

Public PoCSQLi
Published
02 January 2026
Modified
23 February 2026
CVSS Score v4 6.9
Click a component to see what it means
Raw vectorCVSS: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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0050 41th percentile
Risk Priority 41 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-15425 is a medium-severity Injection (CWE-74) vulnerability in Yonyou Ksoa. Its CVSS base score is 6.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 41th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-15425 is a SQL injection vulnerability in Yonyou KSOA 9.0. The flaw affects an unknown function in the file /worksheet/del_user.jsp, specifically within the HTTP GET Parameter Handler component. Attackers can trigger the issue by manipulating the ID argument via HTTP GET requests, leading to improper SQL command execution.

Remote attackers can exploit this vulnerability without privileges (PR:N), user interaction (UI:N), or high complexity (AC:L), over the network (AV:N). Successful exploitation yields limited impacts on confidentiality, integrity, and availability (C:L/I:L/A:L), with a CVSS v3.1 base score of 7.3. The vulnerability is associated with CWE-74 and CWE-89.

References, including GitHub entries with vulnerability details and proof-of-concept code, confirm the exploit has been publicly disclosed and may be utilized. VulDB advisories document the issue, but the vendor was contacted early without any response, and no patches or mitigations are specified.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

A vulnerability was determined in Yonyou KSOA 9.0. The impacted element is an unknown function of the file /worksheet/del_user.jsp of the component HTTP GET Parameter Handler. Executing a manipulation of the argument ID can lead to sql injection. The attack…

more

can be executed remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

CWE(s)
CWE-74CWE-89

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1221 Template Injection Stealth
Adversaries may create or modify references in user document templates to conceal malicious code or force authentication attempts.
attack.mitre.org →
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
T1674 Input Injection Execution
Adversaries may simulate keystrokes on a victim’s computer by various means to perform any type of action on behalf of the user, such as launching the command interpreter using keyboard shortcuts, typing an inline script to be executed,…
attack.mitre.org →
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-51927Same vendor: Yonyou
CVE-2024-24256Same vendor: Yonyou
CVE-2023-1061Shared CWE-74, CWE-89
CVE-2024-40637Shared CWE-74, CWE-89
CVE-2024-7220Shared CWE-74, CWE-89
CVE-2024-10157Shared CWE-74, CWE-89
CVE-2024-6933Shared CWE-74, CWE-89
CVE-2024-1833Shared CWE-74, CWE-89
CVE-2023-7096Shared CWE-74, CWE-89
CVE-2024-7219Shared CWE-74, CWE-89

Affected Assets

yonyou
ksoa
9.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.1
  • V1.2.3
  • V1.2.5
  • V1.2.8

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover SQLi flaws before deployment but does not stop their introduction.

SI-10 Information Input Validation good match

SI-10 directly requires validation of information inputs to reject malformed or special-element content before it reaches downstream parsers.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles require parameterized queries and input sanitization that structurally eliminate SQLi.

SI-4 System Monitoring partial match

System monitoring can identify attempted SQLi exploitation via anomalous queries after the weakness exists.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and output encoding that prevent injection flaws.

PR.AT-02 partial match
prevents

Training raises developer awareness of SQLi risks and can reduce introduction likelihood (partial) but removes none of the actual coding flaw's risk by itself since technical neutralization is still required.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches injection vulnerabilities before release.

A.5.6 Contact with special interest groups partial match
prevents

Early warnings and shared best-practice information help organizations apply the latest remediation techniques against SQL-injection vulnerabilities.

A.5.7 Threat intelligence partial match
prevents

Threat-intelligence feeds that surface new SQL-injection campaigns enable rapid updates to query-construction defenses and detection signatures before exploitation occurs.

A.8.15 Logging partial match
finds

Logging supports detection of injection attempts but does not prevent the weakness.

A.8.16 Monitoring activities partial match
finds

Monitoring activities can identify active injection attacks after they occur.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and output encoding that directly prevent injection flaws.

References