# CVE-2025-7487: JoeyBling SpringBoot_MyBatisPlus upload SysFileController unrestricted upload

> Remote attackers can upload malicious files via the SysFileController upload endpoint, potentially leading to code execution.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 12 Jul 2025
- **Updated:** 14 Jul 2025
- **Also known as:** GHSA-qhgg-j94x-qxmf

## What is CVE-2025-7487?

CVE-2025-7487 is a medium-severity vulnerability in JoeyBling SpringBoot_MyBatisPlus, published on 12 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in JoeyBling SpringBoot_MyBatisPlus up to a6a825513bd688f717dbae3a196bc9c9622fea26. This affects the function SysFileController of the file /file/upload. The manipulation of the argument portraitFile leads to unrestricted upload. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-7487 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7487 is a medium-severity vulnerability in JoeyBling SpringBoot_MyBatisPlus, published on 12 Jul 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-7487 exists.

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

## Sources

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

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