Skip to main content
CVE-2024-28681VulnerabilityPublished Updated

CVE-2024-28681: cms · n/a

Affects cmsSource CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 25 Oct 2026, 19:02 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 15% 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-25.

What to do

Affected software

ProductAffectedFixed in
GitHub777erp/cmspkg:github/777erp/cmsOther 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-28681, organizations should implement robust CSRF protections such as synchronizer tokens (CSRF tokens) in all state-changing forms and requests, especially those handled by /dede/plus_edit.php. Web application firewalls (WAFs) can be configured to detect and block suspicious CSRF attack patterns. Administrators should monitor user activity logs for unusual or unauthorized changes. User education is critical to reduce the risk of social engineering attacks that could lead to exploitation. Until an official patch is released, consider restricting access to the vulnerable endpoint via IP whitelisting or VPNs, and disable or limit the functionality of the plus_edit.php script if feasible. Regularly update and audit the CMS and its plugins to ensure security best practices are followed. Additionally, encourage users to log out when not actively using the CMS to reduce the window of opportunity for CSRF attacks.

Description

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

References

Community reviews

Loading reviews…