dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-34163

CRITICAL · 10.0 CVSS v4.0 Published 2025-08-27
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
Dongsheng Logistics Software exposes an unauthenticated endpoint at /CommMng/Print/UploadMailFile that fails to enforce proper file type validation and access control. An attacker can upload arbitrary files, including executable scripts such as .ashx, via a crafted multipart/form-data POST request. This allows remote code execution on the server, potentially leading to full system compromise. The vulnerability is presumed to affect builds released prior to July 2025 and is remediated in newer versions of the product, though the exact affected range remains undefined. Exploitation evidence was first observed by the Shadowserver Foundation on 2025-07-23 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

Dongsheng Logistics Software contains an unauthenticated file upload vulnerability in the /CommMng/Print/UploadMailFile endpoint. The application fails to validate file types or enforce access controls, allowing attackers to upload malicious .ashx files and execute arbitrary code remotely, leading to full system compromise.

MitigationUpdate to the patched version of Dongsheng Logistics Software released after July 2025; if immediate patching is not feasible, disable network access to the vulnerable endpoint and implement proper authentication and file type validation as compensating controls.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Dongsheng Logistics Software installation
    Locate the application by checking the software name in installed programs (Windows) or reviewing web application banners/footers. Check the software's about page or version information panel.
    Affected if The installed software is Dongsheng Logistics Software and no version information indicates it was updated after July 2025
  2. Verify vulnerable endpoint exists
    Attempt to access the URL path /CommMng/Print/UploadMailFile on the server hosting the application using a web browser or HTTP client. This may require authentication depending on configuration.
    Affected if The endpoint responds with any HTTP status code (200, 401, 403, 500) indicating the path exists and is reachable
  3. Confirm unauthenticated access is possible
    Test the UploadMailFile endpoint without providing any authentication credentials. Observe whether the application accepts the request or returns an authentication error.
    Affected if The endpoint accepts and processes requests without requiring valid authentication tokens or session cookies
  4. Check for missing file type validation
    Send a test upload request to the endpoint with a file that has a non-standard extension (such as .ashx) or a double extension (such as file.txt.ashx). Examine the server response and any stored files.
    Affected if The application accepts and stores files with extensions other than expected safe types like .pdf, .doc, or .jpg without rejecting them or performing content-type validation
  5. Compare installed version to patched release
    Retrieve the current version of Dongsheng Logistics Software from the application configuration, registry (Windows), or administrative interface. Compare against any release notes or version information for patches released after July 2025.
    Affected if The installed version predates or lacks the July 2025 security update that addresses this file upload vulnerability

If Dongsheng Logistics Software is installed, the /CommMng/Print/UploadMailFile endpoint is reachable without authentication, and the application accepts .ashx or other executable file types, the environment is affected by CVE-2025-34163.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the patched version of Dongsheng Logistics Software released after July 2025; if immediate patching is not feasible, disable network access to the vulnerable endpoint and implement proper authentication and file type validation as compensating controls.

Recommended fix Moderate confidence

Latest version of Dongsheng Logistics Software (contact vendor for specific version number)

  1. Contact Dongsheng Software (www.dongshengsoft.com) to obtain the latest version of Dongsheng Logistics Software that includes the security fix for CVE-2025-34163
  2. Upgrade all instances of Dongsheng Logistics Software to the latest available version
  3. Verify that the /CommMng/Print/UploadMailFile endpoint now properly validates file types and requires authentication
  4. If immediate upgrade is not possible, disable or restrict access to the /CommMng/Print/UploadMailFile endpoint at the network level or web application firewall

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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