CVE-2024-52770: DedeV6 · n/a
Affects DedeV6Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 56% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubdedebiz/DedeV6pkg:github/dedebiz/DedeV6Other threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until an official patch is released, organizations should implement several specific mitigations: 1) Restrict access to the /admin/file_manage_control interface using network-level controls such as IP whitelisting or VPN-only access to limit attacker exposure. 2) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious file upload attempts or payloads targeting this endpoint. 3) Monitor server logs and file upload directories for unusual or unexpected files, especially those with executable extensions or scripts. 4) Disable or limit file upload functionality in the admin interface if not strictly necessary. 5) Conduct thorough security audits and penetration testing focused on file upload mechanisms. 6) Segregate the CMS server from critical internal networks to contain potential breaches. 7) Prepare incident response plans for rapid containment and recovery in case of exploitation. 8) Stay updated with vendor announcements and apply patches immediately once available. 9) Consider deploying application-level sandboxing or containerization to limit execution impact of uploaded files. These targeted actions go beyond generic advice and focus on reducing attack surface and early detection.
Description
An arbitrary file upload vulnerability in the component /admin/file_manage_control of DedeBIZ v6.3.0 allows attackers to execute arbitrary code via uploading a crafted file.