CVE-2024-10201
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 · uneditedAdministrative Management System from Wellchoose does not properly validate uploaded file types, allowing remote attackers with regular privileges to upload and execute webshells.
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 Wellchoose Administrative Management System lacks proper server-side file type validation in its upload functionality, allowing authenticated users to bypass client-side checks and upload executable files. When these malicious files are stored within the webroot, they can be accessed and executed, providing attackers with remote code execution capabilities.
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 dataall versionsCVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 Wellchoose Administrative Management System installationSearch for files named 'wellchoose', 'admin', or similar application directories on the server. Check web server document roots for directories containing 'wellchoose' in the name.Affected if The application is present on the server.
-
Locate the file upload functionalityInspect the application's web interface for upload features (profile picture, document upload, file management). Review the application's source code or intercept HTTP requests to identify upload endpoints.Affected if The application has an upload feature that accepts user-submitted files.
-
Check where uploaded files are storedUpload a test file through the application and examine the returned path. Inspect the application's configuration and code to determine if upload_dir or similar settings place files within the webroot (public accessible directory).Affected if Uploaded files are stored in a directory accessible via HTTP (within webroot).
-
Verify if uploaded file types are validated server-sideAttempt to upload a file with an executable extension (.php, .jsp, .asp, .exe, .sh). Intercept the request and modify the Content-Type header or file extension to bypass client-side checks. Check if the server accepts and stores the file.Affected if The server accepts and stores executable file types without rejecting them.
-
Confirm script execution is enabled in upload directoryIf uploaded files are in webroot, access the uploaded test file via a web browser (e.g., http://target.com/uploads/test.php). Check if the server executes the file content instead of serving it as plain text.Affected if The web server executes scripts in the upload directory rather than serving them as downloads.
A user is affected if the Wellchoose Administrative Management System is installed, has an upload feature, stores uploads within the webroot, lacks server-side file type validation, and allows script execution in the upload directory.
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 allowlist-based server-side file validation, store uploaded files outside the webroot or in non-executable storage, and disable script execution in upload directories.
- 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-2024-10201 — 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-2024-10201 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