Skip to main content
VulnerabilityPublished Updated

CVE-2024-22603: cms · Cross-Site Request Forgery (CSRF)

Affects cmsSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 12:54 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubljw11e/cmspkg:github/ljw11e/cmsOther 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-22603, organizations should implement the following specific actions: 1) Apply any available patches or updates from FlyCms developers as soon as they are released. 2) If patches are unavailable, implement server-side anti-CSRF tokens in all state-changing requests, especially for the /system/links/add_link endpoint, to ensure requests originate from legitimate users. 3) Enforce strict SameSite cookie attributes to reduce the risk of CSRF via cross-origin requests. 4) Employ Content Security Policy (CSP) headers to limit the sources of executable scripts and reduce the impact of injected malicious content. 5) Conduct user training to raise awareness about phishing and social engineering tactics that could facilitate CSRF attacks. 6) Monitor web server logs for unusual POST requests to the affected endpoint and implement anomaly detection to identify potential exploitation attempts. 7) Restrict administrative access to trusted networks or VPNs to reduce exposure. 8) Consider implementing multi-factor authentication (MFA) to reduce the risk of session hijacking that could compound CSRF risks.

Description

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

References

Community reviews

Loading reviews…