# CVE-2025-52130: File upload in n/a

> An authenticated attacker can upload arbitrary PHP scripts to WebErpMesv2, leading to remote code execution on the web server.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Aug 2025
- **Updated:** 26 Aug 2025
- **Also known as:** GHSA-jpmf-r2gf-85wf

## What is CVE-2025-52130?

CVE-2025-52130 is a medium-severity vulnerability in n/a, published on 25 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

File upload vulnerability in WebErpMesv2 1.17 in the app/Http/Controllers/FactoryController.php controller. This flaw allows an authenticated attacker to upload arbitrary files, including PHP scripts, which can be accessed via direct GET requests, potentially resulting in remote code execution (RCE) on the web server.

Weakness: CWE-616 (Incomplete Identification of Uploaded File Variables (PHP))

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


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

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

## Is CVE-2025-52130 being exploited?

There is no known exploitation of CVE-2025-52130 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52130 is a medium-severity vulnerability in n/a, published on 25 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-52130 in the wild and no public exploit code.

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-2025-52130/ (Markdown: https://insights.sbomify.com/CVE-2025-52130/index.md)
```

## Sources

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

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