# CVE-2025-4530: feng_ha_ha/megagao ssm-erp/production_ssm File FileController.java handleFileDownload path traversal

> Remote attackers can exploit a path traversal flaw in the file download handler to read arbitrary files from the server.

- **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:** 11 May 2025
- **Updated:** 12 May 2025
- **Also known as:** GHSA-mj22-4v47-rh7c

## What is CVE-2025-4530?

CVE-2025-4530 is a medium-severity path traversal vulnerability in feng_ha_ha production_ssm, published on 11 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in feng_ha_ha/megagao ssm-erp and production_ssm 1.0. It has been declared as problematic. Affected by this vulnerability is the function handleFileDownload of the file FileController.java of the component File Handler. The manipulation leads to path traversal. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. This product is distributed under two entirely different names.

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

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


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

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

## Is CVE-2025-4530 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4530 is a medium-severity path traversal vulnerability in feng_ha_ha production_ssm, published on 11 May 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-4530 exists.

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

## Sources

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

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