# CVE-2024-22939: Cross-site request forgery in n/a

> A Cross-Site Request Forgery vulnerability in FlyCms allows remote attackers to execute arbitrary code via the category edit component.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Feb 2024
- **Updated:** 27 Aug 2024
- **Also known as:** CVE-2024-27692, GHSA-vqx4-jcwp-8g92

## What is CVE-2024-22939?

CVE-2024-22939 is a high-severity vulnerability in n/a, published on 1 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2024-22939?

It affects 1 product.


Products: Sunkaifei Flycms.

## How do I fix CVE-2024-22939?

No fix has been published for CVE-2024-22939 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-22939 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22939 exists.

Public exploit code:

- CVE-2024-22939 (github_poc): https://github.com/NUDTTAN91/CVE-2024-22939

## Other vulnerabilities in n/a

- [CVE-2025-15093](https://insights.sbomify.com/CVE-2025-15093/): sunkaifei FlyCMS Admin Login IndexAdminController.java cross site scripting (medium 5.3)
- [CVE-2025-15094](https://insights.sbomify.com/CVE-2025-15094/): sunkaifei FlyCMS User Login UserController.java userLogin cross site scripting (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22939 and fix it if it is affected.

What it is: CVE-2024-22939 is a high-severity vulnerability in n/a, published on 1 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22939 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-22939/ (Markdown: https://insights.sbomify.com/CVE-2024-22939/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-22939
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-22939
- OSV: https://osv.dev/vulnerability/CVE-2024-22939

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-22939/
Summaries are generated and may contain mistakes; the official description above is the record.