CVE-2026-10205
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 security vulnerability has been detected in Metasoft 美特软件 MetaCRM 6.4.0. The impacted element is an unknown function of the file develop/systparam/softlogo/upload.jsp. Such manipulation leads to unrestricted upload. The attack may be launched remotely. The exploit has been disclosed publicly 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 · moderate confidenceThe vulnerability exists in the upload.jsp file of MetaCRM 6.4.0, allowing unrestricted file upload without proper validation of file types, contents, or filenames. An attacker can remotely upload malicious files (potentially web shells) to the server, leading to remote code execution.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 MetaCRM installation and versionCheck your web application's version information, typically found in the application header, footer, about page, or a version file (e.g., /version, /about, meta tags). Compare the installed version to 6.4.0.Affected if The installed MetaCRM version is exactly 6.4.0 or falls within the affected version range.
-
Locate the vulnerable upload.jsp fileCheck if the file 'develop/systparam/softlogo/upload.jsp' exists in your webroot or application directory. This is the specific path mentioned in the CVE.Affected if The file upload.jsp exists at the path develop/systparam/softlogo/upload.jsp in your deployed application.
-
Verify the upload endpoint is accessibleAttempt to access the URL endpoint directly (e.g., https://yourdomain.com/develop/systparam/softlogo/upload.jsp) via HTTP request to confirm the endpoint is exposed and reachable.Affected if The upload.jsp file responds to HTTP requests, indicating the vulnerable endpoint is publicly accessible.
-
Check if file upload functionality is enabledInspect the upload.jsp configuration and confirm the upload functionality is active. Look for form parameters or functionality that accepts file uploads in the source code.Affected if The upload endpoint accepts file uploads without proper restrictions or validation.
You are affected if MetaCRM version 6.4.0 is installed AND the file develop/systparam/softlogo/upload.jsp exists and is accessible, allowing unrestricted file uploads.
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 dataUntil vendor patch is available: disable or restrict access to the upload functionality via network-level controls or authentication; implement server-side file type validation, content inspection, and filename sanitization; monitor for suspicious file uploads.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10205 — 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-10205 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