CVE-2026-1061
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 · uneditedA vulnerability was detected in xiweicheng TMS up to 2.28.0. Affected by this issue is the function Upload of the file src/main/java/com/lhjz/portal/controller/FileController.java. The manipulation of the argument filename results in unrestricted upload. The attack may be performed from remote. The exploit is now public and may be used.
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 confidenceThe xiweicheng TMS application up to version 2.28.0 contains an unrestricted file upload vulnerability in the FileController.java upload function. By manipulating the filename argument, an attacker can upload arbitrary files to the server, potentially achieving remote code execution if executable payloads are uploaded.
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<= 2.28.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Xiweicheng TMS is deployedCheck your web server for the presence of the TMS application. Look for typical deployment artifacts such as war files, jar files, or unpacked web application directories containing 'tms' or 'xiweicheng' in the path.Affected if The application is deployed on your server
-
Determine the installed versionLocate the application version information. Check the war/jar manifest files, configuration files, or any version.txt/readme files within the deployed application directory. Compare the version number to the affected range (<= 2.28.0).Affected if The installed version is 2.28.0 or lower, or if you cannot confirm a version higher than 2.28.0
-
Verify the Upload endpoint existsCheck if the FileController.java component is present in the deployed application. Look for the upload endpoint path (typically /file/upload or similar patterns in the application's routing). Attempt a HEAD request to common upload paths to confirm accessibility.Affected if The upload endpoint is accessible and the vulnerable FileController component is present
-
Check if file type validation is enforcedInspect the application's web.xml, spring-servlet.xml, or other configuration files for upload filter configurations. Look for FileTypeFilter, content-type validation, or magic byte checking in the application's security configuration.Affected if No file type validation filter is configured, or the upload function accepts files without validating extension or content-type headers
-
Verify upload directory placementExamine the server configuration to determine if the upload directory is located within the webroot (publicly accessible). Check the application.properties or configuration files for the upload.path setting and verify if it points outside the web application directory.Affected if Uploads are stored within the webroot and are directly executable via HTTP
You are affected if Xiweicheng TMS version 2.28.0 or lower is deployed, the FileController upload endpoint is accessible, and no file type validation is configured.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict file type validation (allowlist approach), sanitize filenames, store uploads outside the web root, and disable script execution in the upload directory. Upgrade to version 2.28.1 or later if available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1061 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1061 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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