# CVE-2023-41599: Path traversal in n/a

> Attackers can exploit a directory traversal vulnerability in JFinalCMS to read arbitrary files from the server.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2023
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-g57g-8xw6-gwrx

## What is CVE-2023-41599?

CVE-2023-41599 is a medium-severity path traversal vulnerability in n/a, published on 19 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in the component /common/DownController.java of JFinalCMS v5.0.0 allows attackers to execute a directory traversal.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Jfinalcms Project Jfinalcms.

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

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

## Is CVE-2023-41599 being exploited?

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

Public exploit code:

- JFinalCMS v5.0.0 - Directory Traversal (nuclei): http/cves/2023/CVE-2023-41599.yaml

## Other vulnerabilities in n/a

- [CVE-2024-24029](https://insights.sbomify.com/CVE-2024-24029/): SQL injection in n/a (critical 9.8)
- [CVE-2022-27341](https://insights.sbomify.com/CVE-2022-27341/): SQL injection in n/a (critical 9.8)
- [CVE-2023-49372](https://insights.sbomify.com/CVE-2023-49372/): Cross-Site Request Forgery in JFinalCMS (high 8.8)
- [CVE-2023-49373](https://insights.sbomify.com/CVE-2023-49373/): Cross-Site Request Forgery in JFinalCMS (high 8.8)
- [CVE-2023-49374](https://insights.sbomify.com/CVE-2023-49374/): Cross-Site Request Forgery in JFinalCMS via /admin/slide/update (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-41599 is a medium-severity path traversal vulnerability in n/a, published on 19 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-41599 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-41599/ (Markdown: https://insights.sbomify.com/CVE-2023-41599/index.md)
```

## Sources

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

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