CVE-2023-52073: FlyCms · Cross-Site Request Forgery (CSRF)
Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Jan 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubzouyang0714/cmspkg:github/zouyang0714/cmsOther 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
Immediate mitigation steps include implementing anti-CSRF tokens in all state-changing requests within FlyCms, especially for the /system/site/config_footer_updagte endpoint. Organizations should review and restrict user permissions to minimize the number of users with configuration modification rights. Employing web application firewalls (WAFs) with rules to detect and block CSRF attack patterns can provide an additional layer of defense. Administrators should educate users about the risks of clicking on untrusted links while authenticated to the CMS. Network segmentation and limiting administrative access to trusted IP addresses can reduce exposure. Monitoring logs for unusual configuration changes or access patterns can help detect exploitation attempts early. Finally, organizations should maintain regular backups of configuration data to enable rapid recovery if unauthorized changes occur.
Description
FlyCms v1.0 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /system/site/config_footer_updagte.