CVE-2026-30643
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 · uneditedAn issue was discovered in DedeCMS 5.7.118 allowing attackers to execute code via crafted setup tag values in a module upload.
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 5.7.118 contains a code execution vulnerability where attackers can inject malicious code through crafted setup tag values during module upload. The vulnerability resides in the module installation/setup functionality, allowing remote attackers to achieve arbitrary code execution on the affected system.
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.118CVSS 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.
-
Confirm DedeCMS installationLook for DedeCMS files in the web root directory, typically in folders like /include, /dede, /uploads, or check for the characteristic 'dede' admin folder and index.php with DedeCMS references.Affected if DedeCMS is present on the server
-
Identify DedeCMS versionCheck the version file or common version indicators. In DedeCMS, version information is often found in /data/admin/ver.txt, /include/common.inc.php, or the admin dashboard footer. Compare the version number to 5.7.118.Affected if The installed version is 5.7.118 or lower
-
Verify module upload functionality is accessibleCheck if the module installation feature is enabled by accessing the module upload page typically at /dede/module_main.php or /dede/module_upload.php. Look for the module management section in the admin panel.Affected if Module upload/install functionality is accessible and enabled in the admin panel
-
Inspect for unauthorized module installationsReview the /include/modules/ or /uploads/modules/ directory for any unfamiliar or recently added module folders. Check /data/module/ for module configuration files that may contain injected setup tags.Affected if Unexpected modules exist or suspicious setup tag configurations are found in module files
-
Review web server logs for module upload activityCheck web server access logs (Apache/nginx) for POST requests to module_upload.php, module_main.php, or similar module installation endpoints, especially with unusual parameter patterns.Affected if Logs show module upload or installation requests from unexpected sources
A system is affected if it runs DedeCMS version 5.7.118 or lower AND has the module upload/install functionality accessible and enabled.
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 dataRestrict or disable module upload functionality until an official patch is released. Implement strict input validation on setup tag parameters and apply principle of least privilege to module installation permissions.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30643 — 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-30643 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