# CVE-2021-48014: FineReport 9.0 Unauthenticated Path Traversal File Write via ReportServer


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-wxvw-chm6-9q9h

## What is CVE-2021-48014?

CVE-2021-48014 is a critical vulnerability in FanRuan FineReport, published on 22 Oct 2026. 

### Official description

FineReport 9.0 contains a path traversal vulnerability in the /WebReport/ReportServer design_save_svg operation that allows unauthenticated attackers to write arbitrary files via the filePath parameter. Attackers can send a POST request with directory traversal sequences in filePath and a __CONTENT__ payload to write a JSP webshell and achieve remote code execution. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-14.

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

## Which versions are affected by CVE-2021-48014?


## How do I fix CVE-2021-48014?

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

## Is CVE-2021-48014 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-48014 and fix it if it is affected.

What it is: CVE-2021-48014 is a critical vulnerability in FanRuan FineReport, published on 22 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-48014 exists.

Affected product: FanRuan FineReport. 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-2021-48014/ (Markdown: https://insights.sbomify.com/CVE-2021-48014/index.md)
```

## Sources

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

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