Skip to main content
CVE-2024-28677VulnerabilityPublished Updated

CVE-2024-28677: dedecms · n/a

Affects dedecmsSource CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 07:57 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Mar 2024

  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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
GitHub777erp/cms/dedecmspkg:github/777erp/cms/dedecmsOther threatsAffected
  • =5.7
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-28677, organizations should implement robust anti-CSRF protections such as synchronizer tokens or double-submit cookies on all state-changing requests, especially those involving article keyword management. Web application firewalls (WAFs) can be configured to detect and block suspicious CSRF patterns or anomalous requests to /dede/article_keywords_main.php. Administrators should enforce strict session management and consider reducing the number of users with privileges to modify article keywords. User education is critical to avoid clicking on untrusted links while authenticated to the CMS. Monitoring web server logs for unusual POST requests to the vulnerable endpoint can help detect attempted exploitation. Until an official patch is released, consider temporarily disabling or restricting access to the affected functionality if feasible. Regularly check for vendor updates and apply patches promptly once available. Additionally, implementing Content Security Policy (CSP) headers can help reduce the risk of CSRF by limiting the sources of executable scripts.

Description

DedeCMS v5.7 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /dede/article_keywords_main.php.

References

Community reviews

Loading reviews…