# CVE-2023-4659: Cross-Site Request Forgery in Free5Gc

> An attacker can perform administrative actions like creating or deleting users by manipulating tokens or sending requests without authentication.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2023
- **Updated:** 20 Sep 2024
- **Also known as:** GHSA-cg7m-7w47-wjq6

## What is CVE-2023-4659?

CVE-2023-4659 is a critical vulnerability in Free5Gc Open5Gc, published on 2 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cross-Site Request Forgery vulnerability, whose exploitation could allow an attacker to perform different actions on the platform as an administrator, simply by changing the token value to "admin". It is also possible to perform POST, GET and DELETE requests without any token value. Therefore, an unprivileged remote user is able to create, delete and modify users within theapplication.

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

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

It affects 1 product.


Products: Free5gc Webconsole.

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

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

## Is CVE-2023-4659 being exploited?

There is no known exploitation of CVE-2023-4659 in the wild and no public exploit code.

## Other vulnerabilities in Free5Gc Open5Gc

- [CVE-2026-40246](https://insights.sbomify.com/CVE-2026-40246/): free5gc UDR improper path validation allows unauthenticated deletion of Traffic Influence Subscriptions (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-4659 is a critical vulnerability in Free5Gc Open5Gc, published on 2 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-4659 in the wild and no public exploit code.

Affected product: Free5Gc Open5Gc. 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-4659/ (Markdown: https://insights.sbomify.com/CVE-2023-4659/index.md)
```

## Sources

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

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