# CVE-2025-3214: JFinal CMS readTemplate engine.getTemplate path traversal

> Remote attackers can exploit path traversal in JFinal CMS to read arbitrary files, though the vendor disputes this as a bug.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Apr 2025
- **Updated:** 4 Apr 2025
- **Also known as:** GHSA-g9jw-53r4-8v8g

## What is CVE-2025-3214?

CVE-2025-3214 is a medium-severity path traversal vulnerability in JFinal CMS, published on 4 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in JFinal CMS up to 5.2.4 and classified as problematic. Affected by this vulnerability is the function engine.getTemplate of the file /readTemplate. The manipulation of the argument template leads to path traversal. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The real existence of this vulnerability is still doubted at the moment. The vendor explains that this is not a bug but a feature.

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

## Which versions are affected by CVE-2025-3214?


## How do I fix CVE-2025-3214?

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

## Is CVE-2025-3214 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3214 and fix it if it is affected.

What it is: CVE-2025-3214 is a medium-severity path traversal vulnerability in JFinal CMS, published on 4 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3214 exists.

Affected product: JFinal CMS. 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-2025-3214/ (Markdown: https://insights.sbomify.com/CVE-2025-3214/index.md)
```

## Sources

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

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