VulnerabilityPublished 19 Jan 2026Updated 23 Feb 2026

CVE-2026-1131: 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.5% chance of exploitation in 30 days – higher than 45% 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 19 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
YonyouKSOA	Affected =9.0	Fixed in–

CPE configurations (1)

cpe:2.3:a:yonyou:ksoa:*:*:*:*:*:*:*:*

AI-suggested

Given the absence of an official patch, organizations should implement immediate compensating controls. First, restrict external access to the /kmc/save_catalog.jsp endpoint via network segmentation, firewalls, or web application firewalls (WAFs) with rules to detect and block SQL injection patterns targeting the 'catalogid' parameter. Employ input validation and sanitization at the application or proxy level to filter malicious inputs. Monitor logs for suspicious query patterns or repeated access attempts to the vulnerable endpoint. Conduct thorough security assessments and penetration tests to identify exploitation attempts. If feasible, consider temporarily disabling or restricting the vulnerable functionality until a vendor patch is released. Engage with Yonyou support channels for updates and advocate for timely remediation. Additionally, maintain regular backups and ensure incident response plans are updated to handle potential data compromise scenarios.

Description

A vulnerability has been found in Yonyou KSOA 9.0. Impacted is an unknown function of the file /kmc/save_catalog.jsp of the component HTTP GET Parameter Handler. Such manipulation of the argument catalogid leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public 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 can have significant consequences for organizations using this software. Successful exploitation could allow attackers to access sensitive corporate data stored in backend databases, modify or delete records, and potentially disrupt application functionality. This could lead to data breaches, loss of data integrity, and service outages, impacting business operations and reputation. Since the vulnerability requires no authentication and can be exploited remotely, it increases the attack surface and risk of automated attacks or exploitation by opportunistic threat actors. The lack of vendor response and patch availability prolongs exposure, increasing the window for potential attacks. Organizations in sectors relying heavily on Yonyou KSOA, such as finance, manufacturing, and government in regions where the product is prevalent, face elevated risks. The impact extends beyond confidentiality to integrity and availability, potentially affecting compliance and operational continuity.

Summary

CVE-2026-1131 is a SQL injection vulnerability identified in Yonyou KSOA version 9.0, a widely used enterprise application platform. The flaw exists in the handling of the 'catalogid' parameter within the /kmc/save_catalog.jsp endpoint, which processes HTTP GET requests. Due to insufficient input validation and sanitization, attackers can inject arbitrary SQL commands remotely without requiring authentication or user interaction. This vulnerability allows attackers to manipulate backend database queries, potentially leading to unauthorized data access, data modification, or disruption of service. The vulnerability has been publicly disclosed, and although no active exploitation has been reported, the availability of exploit details increases the risk of attacks. The vendor was notified but has not issued any response or patch, leaving systems exposed. The CVSS 4.0 base score is 6.9 (medium severity), reflecting the network attack vector, low complexity, and no required privileges or user interaction. The vulnerability impacts confidentiality, integrity, and availability to a limited extent due to the nature of the injection and the affected component. Organizations relying on Yonyou KSOA 9.0 should be aware of this risk and take immediate steps to mitigate exposure.

References

Community reviews

Loading reviews…