Skip to main content
CVE-2024-22593VulnerabilityPublished Updated

CVE-2024-22593: cms2 · n/a

Affects cms2Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% 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:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Jan 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
GitHubysuzhangbin/cms2pkg:github/ysuzhangbin/cms2Other threatsAffected
  • =1.0
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-22593, organizations should immediately implement the following measures: 1) Restrict administrative access to trusted networks or VPNs to reduce exposure to external attackers. 2) Educate administrators on the risks of CSRF and the importance of avoiding clicking on suspicious links or visiting untrusted websites while logged into the CMS. 3) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious POST requests to the /system/admin/add_group_save endpoint. 4) Implement browser security policies such as SameSite cookies to limit cross-origin requests. 5) Monitor administrative logs for unusual group creation or modification activities. 6) If possible, disable or limit the use of the vulnerable endpoint until a patch is released. 7) Engage with FlyCms developers or community to obtain or expedite a security patch. 8) Consider deploying multi-factor authentication (MFA) for administrative accounts to add an additional layer of defense. These steps go beyond generic advice by focusing on immediate containment and detection strategies in the absence of an official patch.

Description

FlyCms v1.0 contains a Cross-Site Request Forgery (CSRF) vulnerability via /system/admin/add_group_save

References

Community reviews

Loading reviews…