# CVE-2025-1165: Lumsoft ERP FileUploadApi.ashx DoWebUpload unrestricted upload

> An attacker can upload malicious files to Lumsoft ERP via the FileUploadApi endpoint, potentially leading to remote code execution.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2025
- **Updated:** 18 Feb 2025
- **Also known as:** GHSA-rvrw-q6hf-fq9h

## What is CVE-2025-1165?

CVE-2025-1165 is a medium-severity vulnerability in Lumsoft ERP, published on 11 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in Lumsoft ERP 8. Affected is the function DoUpload/DoWebUpload of the file /Api/FileUploadApi.ashx. The manipulation of the argument file leads to unrestricted upload. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

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

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


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

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

## Is CVE-2025-1165 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1165 is a medium-severity vulnerability in Lumsoft ERP, published on 11 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1165 exists.

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

## Sources

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

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