VulnerabilityPublished 19 Jan 2026Updated 23 Feb 2026

CVE-2026-1179: 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.4% chance of exploitation in 30 days – higher than 35% 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

Given the lack of an official patch from Yonyou, organizations should implement layered defenses to mitigate CVE-2026-1179. First, apply strict input validation and sanitization on all user-supplied parameters, especially 'folderid', to block malicious SQL payloads. Deploy Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the vulnerable endpoint. Monitor web server and database logs for unusual query patterns or repeated access attempts to /kmf/user_popedom.jsp. Restrict network access to the affected service to trusted IP ranges where feasible, reducing exposure. Conduct regular security assessments and penetration tests focused on SQL injection vectors. Consider isolating or segmenting the affected application components to limit lateral movement if compromised. Maintain up-to-date backups to enable recovery from potential data tampering. Engage with Yonyou support channels persistently for updates or patches. Finally, educate development and operations teams about secure coding practices to prevent similar vulnerabilities in future deployments.

Description

A vulnerability was detected in Yonyou KSOA 9.0. This affects an unknown part of the file /kmf/user_popedom.jsp of the component HTTP GET Parameter Handler. The manipulation of the argument folderid results in sql injection. The attack can be launched remotely. The exploit is now public 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-1179 is substantial for organizations using Yonyou KSOA 9.0. Exploitation can lead to unauthorized access to sensitive data, including user permissions and potentially other confidential business information stored in the backend database. Attackers could manipulate or delete data, undermining data integrity and availability of critical services. Since the vulnerability requires no authentication and can be exploited remotely, it poses a high risk of widespread compromise if left unmitigated. This can result in data breaches, operational disruptions, and reputational damage. The absence of vendor patches increases the window of exposure, potentially inviting targeted attacks or automated exploitation campaigns. Organizations in sectors relying heavily on Yonyou software, such as finance, government, and manufacturing, may face regulatory and compliance consequences if exploited. The medium CVSS score reflects partial but meaningful impacts across confidentiality, integrity, and availability, emphasizing the need for urgent attention.

Summary

CVE-2026-1179 identifies a SQL injection vulnerability in Yonyou KSOA version 9.0, a widely used enterprise application platform. The vulnerability resides in the HTTP GET parameter 'folderid' within the /kmf/user_popedom.jsp component. An attacker can remotely craft malicious input to this parameter, which is improperly sanitized, allowing arbitrary SQL commands to be injected and executed by the backend database. This can lead to unauthorized data retrieval, modification, or deletion. The vulnerability requires no authentication or user interaction, increasing its risk profile. The CVSS 4.0 vector (AV:N/AC:L/AT:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P) reflects network attack vector, low attack complexity, no privileges or user interaction needed, and partial impacts on confidentiality, integrity, and availability. The lack of vendor engagement complicates remediation efforts, forcing organizations to rely on compensating controls. This vulnerability affects a critical access control component, potentially exposing sensitive user permissions and data. Given Yonyou's prominence in Asia-Pacific enterprise environments, the threat is regionally significant.

References

Community reviews

Loading reviews…