CVE-2026-30643
Received Received - Intake
Remote Code Execution via Module Upload in DedeCMS

Publication date: 2026-04-01

Last updated on: 2026-04-06

Assigner: MITRE

Description
An issue was discovered in DedeCMS 5.7.118 allowing attackers to execute code via crafted setup tag values in a module upload.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-01
Last Modified
2026-04-06
Generated
2026-05-07
AI Q&A
2026-04-01
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
dedecms dedecms to 5.7.118 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-94 The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-30643 is a vulnerability in DedeCMS version 5.7.118 that allows attackers with backend access to execute arbitrary PHP code on the server.

The issue arises from the module upload functionality where authenticated users can upload crafted XML module files containing a base64-encoded PHP payload inside a <setup> tag.

During module installation, this payload is decoded and written to a PHP file on the server, which is then included and executed, enabling remote code execution.

  • Attackers log into the backend, upload a malicious XML module, trigger the installation, and then execute arbitrary commands via the created PHP file.

How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability in DedeCMS 5.7.118 allows authenticated attackers to execute arbitrary PHP code on the server via crafted module uploads, leading to remote code execution.

Such unauthorized code execution can lead to unauthorized access, data breaches, and potential manipulation or exfiltration of sensitive data.

This can negatively impact compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive data against unauthorized access and breaches.

Organizations using vulnerable versions of DedeCMS may face increased risk of non-compliance due to potential data compromise stemming from exploitation of this vulnerability.


How can this vulnerability impact me? :

This vulnerability can lead to remote code execution on the affected server, allowing attackers to run arbitrary system commands.

An attacker with backend access could gain full control over the server, potentially leading to data theft, server compromise, defacement, or further attacks within the network.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by checking for the presence of suspicious PHP files created in the data/module/ directory, specifically files named with a hash followed by '-setup.php'. These files are generated when a crafted module XML with a base64-encoded PHP payload is uploaded and executed.

You can also monitor web server access logs for requests to URLs like data/module/<hash>-setup.php with query parameters such as ?cmd=whoami, which indicate attempts to execute arbitrary commands.

Suggested commands to detect exploitation attempts or presence of malicious files include:

  • List suspicious PHP files in the module data directory: ls -l data/module/*-setup.php
  • Search web server logs for access to these PHP files: grep 'data/module/.*-setup.php' /var/log/apache2/access.log
  • Check for recent file creation or modification times in the data/module directory: find data/module/ -name '*-setup.php' -mtime -7
  • If you have backend access, review uploaded module XML files for suspicious base64-encoded <setup> tags containing PHP code.

What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include restricting backend access to trusted users only, as exploitation requires authenticated backend login.

Disable or restrict the module upload and installation functionality if it is not needed.

Monitor and remove any suspicious PHP files in the data/module/ directory, especially those matching '*-setup.php'.

Implement strict input validation and sanitization on uploaded module XML files to prevent execution of arbitrary PHP code.

If possible, update DedeCMS to a version that patches this vulnerability once available.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart