dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2022-50973

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-02
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 7 weeks old

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
Yonyou KSOA 9.0 contains an unauthenticated arbitrary file upload vulnerability in the com.sksoft.bill.ImageUpload servlet that allows unauthenticated attackers to upload arbitrary files by submitting a POST request with attacker-controlled filepath and filename parameters without any authentication, file type, extension, or content validation. Attackers can upload a JSP webshell by specifying a malicious filename and root filepath, with the uploaded file stored under the pictures directory and directly executed by the web server, resulting in unauthenticated remote code execution. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-11-07 (UTC).

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

Yonyou KSOA 9.0 contains an unauthenticated arbitrary file upload vulnerability in the com.sksoft.bill.ImageUpload servlet. Attackers can upload arbitrary files including JSP webshells by submitting POST requests with attacker-controlled filepath and filename parameters without any authentication, file type, extension, or content validation. The uploaded files are stored in the pictures directory and directly executed, resulting in unauthenticated remote code execution.

MitigationImmediately restrict network access to the affected ImageUpload servlet and contact Yonyou for an official patch. Implement WAF rules to block malicious file upload patterns and validate file types/extensions server-side until a patch is available.

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

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 if Yonyou KSOA is installed
    Check for the presence of Yonyou KSOA installation directories, typically found under the application server webroot (e.g., in Tomcat under webapps/ or similar). Look for directories named 'ksoa' or 'KSOA', and examine any startup scripts or configuration files that reference the product.
    Affected if Yonyou KSOA 9.0 is present on the system
  2. Verify the ImageUpload servlet exists
    Examine the deployed application WEB-INF/web.xml file for the 'com.sksoft.bill.ImageUpload' servlet mapping. This file is typically located in the KSOA deployment directory under WEB-INF/.
    Affected if The ImageUpload servlet is defined in the application configuration, indicating the vulnerable component is deployed
  3. Check if the servlet is network-accessible
    Send a POST request to the ImageUpload endpoint. The URL pattern typically follows the servlet mapping from web.xml, commonly appearing as /bill/ImageUpload or similar paths under the KSOA context root.
    Affected if The servlet responds to HTTP requests without requiring authentication, confirming it is network-accessible
  4. Inspect the upload directory for suspicious files
    Locate the 'pictures' directory within the KSOA deployment (typically under the web root or a subdirectory accessible via the web server). List all files and check for unexpected extensions such as .jsp, .jspx, .asp, .php, or shell scripts.
    Affected if Unexpected files with executable extensions (especially JSP files) are present in the pictures directory or any web-accessible directory
  5. Review web server access logs for upload attempts
    Examine HTTP access logs from the web server (IIS, Apache, or the Java application server) for POST requests to the ImageUpload endpoint. Look for patterns with unusual filename parameters or file types.
    Affected if Logs show POST requests to the ImageUpload servlet with suspicious filename, filepath, or content patterns

A user is affected if Yonyou KSOA 9.0 is installed and the ImageUpload servlet is network-accessible without authentication, or if suspicious executable files are found in web-accessible directories.

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

Immediately restrict network access to the affected ImageUpload servlet and contact Yonyou for an official patch. Implement WAF rules to block malicious file upload patterns and validate file types/extensions server-side until a patch is available.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-50973 — 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-2022-50973 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