CVE-2024-22939: Cross Site Request Forgery vulnerability in FlyCms v.1.0 allows a remote attacker to execute arbitrary code vi

This month

HIGH 8.8DOWNGRADE

CVE-2024-22939 is a high-severity flaw (CVSS 8.8) affecting flycms. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Cross Site Request Forgery vulnerability in FlyCms v.1.0 allows a remote attacker to execute arbitrary code via the system/article/category_edit component.

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.7% (top 47%)
CISA exploited list	No
Weakness	CWE-352
Published	2024-02-29
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: sunkaifei

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-02-29 01:44 UTCPublished CVE record published
2026-06-17 07:11 UTCUpdated Record last modified

sunkaifei flycms DOWNGRADE

Affected: 1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0

1. Check installed version

apt-cache policy flycms || rpm -q flycms || flycms --version

2. No fixed release: DOWNGRADE to a release before 1.0 (Debian / Ubuntu)

apt-cache madison flycms sudo apt install flycms=<VERSION_BEFORE_1.0> sudo apt-mark hold flycms

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list flycms sudo dnf downgrade flycms-<VERSION_BEFORE_1.0> sudo dnf versionlock add flycms

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-22939?

flycms: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-22939 being exploited?

CVE-2024-22939 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-22939 affect?

CVE-2024-22939 affects flycms. Severity is high (CVSS 8.8). Cross Site Request Forgery vulnerability in FlyCms v.1.0 allows a remote attacker to execute arbitrary code via the system/article/category_edit component.

How urgent is CVE-2024-22939?

Priority 49/100. High severity; Public exploit reference

Related CVEs

CVE-2025-15093 MEDIUM 4.3 UPGRADE A security flaw has been discovered in sunkaifei FlyCMS up to abbaa5a8daefb146ad4d61027035026b052cb414
CVE-2025-15094 MEDIUM 4.3 UPGRADE A weakness has been identified in sunkaifei FlyCMS up to abbaa5a8daefb146ad4d61027035026b052cb414
CVE-2024-27694 HIGH 7.4 DOWNGRADE FlyCms v1.0 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via the /system/share/
CVE-2024-22819 HIGH 8.8 DOWNGRADE FlyCms v1.0 contains a Cross-Site Request Forgery (CSRF) vulnerability via /system/email/email_templets_update
CVE-2024-22818 HIGH 8.8 DOWNGRADE FlyCms v1.0 contains a Cross-Site Request Forgery (CSRF) vulnerbility via /system/site/filterKeyword_save

References

← Back to latest CVEs