VulnerabilityPublished 19 Jan 2026Updated 23 Feb 2026

CVE-2026-1130: Yonyou KSOA · SQL Injection

Affects Yonyou KSOASource CVE Database V5

Public exploit available · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 14:05 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 44% 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–
GitHubyonyou/ksoa`pkg:github/yonyou/ksoa`Other threats	Affected =9.0	Fixed in–

CPE configurations (1)

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

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-1130, organizations should implement multiple layers of defense. First, deploy web application firewalls (WAFs) configured to detect and block SQL injection attempts targeting the vulnerable endpoint and parameter. Second, apply strict input validation and sanitization on all user-supplied data, especially the 'ID' parameter in the /worksheet/worksadd_plan.jsp request, using allowlists and parameterized queries where possible. Third, restrict direct internet access to the affected application by placing it behind VPNs or internal networks and segmenting the network to limit attacker lateral movement. Fourth, monitor logs and network traffic for unusual database queries or access patterns indicative of exploitation attempts. Fifth, maintain regular backups of critical databases to enable recovery in case of data corruption or deletion. Finally, engage with Yonyou for updates or patches and plan for timely application once available. Organizations should also consider conducting penetration testing focused on SQL injection to identify and remediate similar vulnerabilities proactively.

Description

A flaw has been found in Yonyou KSOA 9.0. This issue affects some unknown processing of the file /worksheet/worksadd_plan.jsp of the component HTTP GET Parameter Handler. This manipulation of the argument ID causes sql injection. It is possible to initiate the attack remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The impact of CVE-2026-1130 on organizations can be significant. Successful exploitation allows attackers to execute arbitrary SQL commands on the backend database, potentially leading to unauthorized disclosure of sensitive corporate data, including financial records, employee information, and intellectual property. Data integrity may be compromised through unauthorized modifications or deletions, which can disrupt business operations and damage trust. Availability could also be affected if attackers execute destructive queries or cause database crashes. Since the vulnerability requires no authentication or user interaction, it can be exploited by remote attackers with minimal effort, increasing the likelihood of attacks. The public availability of exploit code further raises the risk of widespread exploitation. Organizations relying on Yonyou KSOA 9.0, especially in sectors handling sensitive data, face increased exposure to data breaches, regulatory penalties, and reputational harm. The absence of vendor patches means organizations must rely on compensating controls to mitigate risk until a fix is available.

Summary

CVE-2026-1130 is a SQL injection vulnerability affecting Yonyou KSOA version 9.0, a business management software widely used in enterprise environments. The vulnerability resides in the HTTP GET parameter handler for the /worksheet/worksadd_plan.jsp endpoint, where the 'ID' parameter is improperly sanitized, allowing attackers to inject malicious SQL queries. This flaw can be exploited remotely without any authentication or user interaction, making it highly accessible to attackers. The injection can lead to unauthorized data access, modification, or deletion, potentially compromising the confidentiality, integrity, and availability of the backend database. The CVSS 4.0 score of 6.9 reflects a medium severity level, with network attack vector, low attack complexity, and no privileges or user interaction required. The vulnerability affects only version 9.0 of KSOA, and no information about other versions is provided. Given the nature of SQL injection, attackers could leverage this flaw to extract sensitive business data, escalate privileges, or disrupt services. The lack of vendor response and patch availability necessitates immediate defensive measures by affected organizations.

References

Community reviews

Loading reviews…