# CVE-2023-52074: Cross-site request forgery in n/a

> An attacker can trick users into modifying website configuration settings in FlyCms via a Cross-Site Request Forgery vulnerability.

- **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:** 8 Jan 2024
- **Updated:** 13 Jun 2025
- **Also known as:** GHSA-v875-9cwm-7qjc

## What is CVE-2023-52074?

CVE-2023-52074 is a high-severity vulnerability in n/a, published on 8 Jan 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

FlyCms v1.0 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component system/site/webconfig_updagte.

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

## Which versions are affected by CVE-2023-52074?

It affects 1 product.


Products: Flycms Project Flycms.

## How do I fix CVE-2023-52074?

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

## Is CVE-2023-52074 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-22568](https://insights.sbomify.com/CVE-2024-22568/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2024-22591](https://insights.sbomify.com/CVE-2024-22591/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2024-22592](https://insights.sbomify.com/CVE-2024-22592/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2024-22593](https://insights.sbomify.com/CVE-2024-22593/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2024-22601](https://insights.sbomify.com/CVE-2024-22601/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-52074 and fix it if it is affected.

What it is: CVE-2023-52074 is a high-severity vulnerability in n/a, published on 8 Jan 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-2023-52074 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-2023-52074/ (Markdown: https://insights.sbomify.com/CVE-2023-52074/index.md)
```

## Sources

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

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