Skip to main content
VulnerabilityPublished

CVE-2026-30643: DedeCMS · Code Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

  1. Monitor official DedeCMS channels closely for security patches addressing CVE-2026-30643 and apply them immediately upon release.
  2. Until a patch is available, restrict module upload functionality to trusted administrators only and disable any unnecessary upload features.
  3. Implement strict input validation and sanitization on all user-supplied data, especially within module upload and setup tag processing components.
  4. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious payloads targeting the setup tag upload vector.
  5. Conduct regular security audits and code reviews focusing on input handling and module upload mechanisms.
  6. Monitor server and application logs for unusual activity indicative of exploitation attempts, such as unexpected file uploads or execution of unknown code.
  7. Isolate web servers running DedeCMS from critical internal networks to limit lateral movement in case of compromise.
  8. Educate administrators and developers about the risks associated with module uploads and secure coding practices.
  9. Consider deploying intrusion detection/prevention systems (IDS/IPS) tuned to detect exploitation patterns related to CWE-94 vulnerabilities.
  10. Maintain regular backups of website content and configurations to enable rapid recovery if an attack occurs.

Description

An issue was discovered in DedeCMS 5.7.118 allowing attackers to execute code via crafted setup tag values in a module upload.

References

Community reviews

Loading reviews…