CVE-2026-1122VulnerabilityPublished 18 Jan 2026Updated 23 Feb 2026

CVE-2026-1122: Yonyou KSOA · SQL Injection

Affects Yonyou KSOASource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 06:26 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 18 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-26.

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
YonyouKSOA	Affected =9.0	Fixed in–

CPE configurations (1)

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

AI-suggested

1. Implement Web Application Firewall (WAF) rules to detect and block malicious SQL injection payloads targeting the 'ID' parameter in /worksheet/work_info.jsp requests. 2. Employ strict input validation and sanitization at the application or proxy level to reject unexpected or malformed input values for the 'ID' parameter. 3. Restrict network access to the affected application endpoints to trusted internal IPs or VPN users where feasible, reducing exposure to external attackers. 4. Monitor application logs and network traffic for unusual query patterns or error messages indicative of SQL injection attempts. 5. If possible, deploy database activity monitoring to detect anomalous queries originating from the KSOA application. 6. Engage with Yonyou support channels to request official patches or updates and track any future advisories. 7. Consider isolating or segmenting the affected application environment to limit lateral movement in case of compromise. 8. Prepare incident response plans specific to SQL injection attacks, including data backup and recovery strategies. 9. Evaluate alternative software solutions if patching or mitigation is not feasible in the short term.

Description

A vulnerability was determined in Yonyou KSOA 9.0. This impacts an unknown function of the file /worksheet/work_info.jsp of the component HTTP GET Parameter Handler. This manipulation of the argument ID causes sql injection. The attack may be initiated 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.

Impact

The SQL injection vulnerability in Yonyou KSOA 9.0 can lead to unauthorized access and manipulation of sensitive business data stored in backend databases. Exploitation could allow attackers to extract confidential information, alter records, or delete critical data, potentially disrupting business operations. The compromise of data integrity and availability could affect financial reporting, workflow management, and other enterprise functions relying on KSOA. Since the vulnerability requires no authentication and can be exploited remotely, it poses a significant risk of widespread exploitation if left unmitigated. Organizations in sectors such as finance, manufacturing, and government using Yonyou KSOA may face data breaches, regulatory penalties, and reputational damage. The absence of vendor patches increases the window of exposure, making timely mitigation critical to prevent potential attacks.

Summary

CVE-2026-1122 identifies a SQL injection vulnerability in Yonyou KSOA version 9.0, specifically within the HTTP GET parameter handler of the /worksheet/work_info.jsp component. The vulnerability arises from improper sanitization or validation of the 'ID' parameter, which attackers can manipulate to inject arbitrary SQL queries. This injection flaw allows remote attackers to execute unauthorized SQL commands on the backend database without requiring authentication or user interaction. The vulnerability has a CVSS 4.0 base score of 6.9, indicating a medium severity level, with an attack vector of network (remote), low attack complexity, and no privileges or user interaction needed. The impact includes potential unauthorized disclosure, modification, or deletion of data, which compromises confidentiality, integrity, and availability to a limited extent. The vendor has been notified but has not provided a patch or mitigation guidance, and while public exploit code exists, no active exploitation has been reported. This vulnerability primarily affects organizations using Yonyou KSOA 9.0, a business software suite widely used in China and other Asian markets. The lack of a patch and public exploit availability increases the urgency for affected organizations to implement defensive measures.

References

Community reviews

Loading reviews…