CVE-2023-40784
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 · uneditedDedeCMS 5.7.102 has a File Upload vulnerability via uploads/dede/module_make.php.
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 confidenceDedeCMS version 5.7.102 contains an arbitrary file upload vulnerability in the module_make.php script located in the /uploads/dede/ admin directory. This vulnerability allows attackers to upload malicious files (such as web shells) directly to the server, potentially achieving remote code execution.
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= 5.7.102CVSS 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 DedeCMS is installedLook for the /uploads/dede/ directory or common DedeCMS files such as index.php, dede/login.php, or data/common.inc.php on your web server.Affected if The DedeCMS files and directory structure are present on the server.
-
Determine the installed DedeCMS versionCheck the version file or footer of the admin panel. Common locations include /include/common.inc.php (search for 'ver' or 'version'), or access the admin login page and view the page source for version information.Affected if The installed version is exactly 5.7.102.
-
Locate the vulnerable module_make.php fileCheck if the file /uploads/dede/module_make.php exists on your web server by attempting to access it via HTTP request or checking the filesystem directly.Affected if The file module_make.php exists in the /uploads/dede/ directory.
-
Verify the file is accessible via webSend an HTTP GET request to https://yourdomain.com/uploads/dede/module_make.php and check for any response (even an error page indicates the file is web-accessible).Affected if The script returns any HTTP response, indicating it is reachable via the web.
You are affected if DedeCMS version 5.7.102 is installed and the /uploads/dede/module_make.php file is present and accessible on the web server.
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 dataImmediately restrict or disable access to the module_make.php file (e.g., via .htaccess rules or web server configuration) if not required for legitimate module operations. If the file is unused in the deployment, remove it entirely. Implement strict file type validation and authentication requirements on all upload endpoints.
- 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-2023-40784 — 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-2023-40784 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