dbcve.org
KsoaApplication · Yonyou

CVE-2026-1179

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in Yonyou KSOA 9.0 allows remote attackers to inject arbitrary SQL commands via the folderid GET parameter in /kmf/user_popedom.jsp. The lack of input sanitization in the HTTP GET Parameter Handler component enables complete database compromise.

MitigationImplement parameterized queries or prepared statements for all database interactions involving user-supplied input. Alternatively, deploy a WAF to block SQL injection attempts until code-level fixes can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
KsoaApplication
Affected:= 9.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Yonyou KSOA installation version
    Locate the version information in the application installation directory, typically found in version manifests, about pages, or configuration files. Check installation logs or contact the system administrator for version details.
    Affected if The installed version is Yonyou KSOA 9.0 specifically.
  2. Locate vulnerable JSP endpoint
    Check if the file /kmf/user_popedom.jsp exists in the web application root directory. This file is part of the KM (Knowledge Management) framework in KSOA.
    Affected if The file /kmf/user_popedom.jsp exists and is deployed on the server.
  3. Verify endpoint accessibility
    Attempt an HTTP GET request to http://[host]/kmf/user_popedom.jsp (without parameters) to confirm the endpoint is accessible and responds.
    Affected if The endpoint returns an HTTP 200 response indicating it is active.
  4. Inspect folderid parameter handling
    Send a GET request with a test folderid parameter (e.g., ?folderid=1) and examine how the application processes it. Check if the input is used directly in SQL queries without apparent sanitization or parameterized queries.
    Affected if The folderid parameter is accepted and used in SQL queries without proper input validation or parameterized queries.
  5. Review database query logs
    Examine database query logs or web application firewall (WAF) logs for SQL injection patterns in the folderid parameter. Look for unusual SQL syntax, OR 1=1, UNION SELECT, or other injection indicators.
    Affected if SQL injection patterns are present in requests to the folderid parameter.

You are affected if you are running Yonyou KSOA version 9.0 and the /kmf/user_popedom.jsp endpoint with the folderid parameter is accessible and processes input without SQL injection protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries or prepared statements for all database interactions involving user-supplied input. Alternatively, deploy a WAF to block SQL injection attempts until code-level fixes can be applied.

Fix this in Ksoa Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1179 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1179 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data