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

> Unauthenticated attackers can upload executable PHP files to achieve remote code execution due to missing validation in the payment update module.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2025
- **Updated:** 10 May 2025
- **Also known as:** GHSA-hxm6-cc9v-9f63

## What is CVE-2025-46191?

CVE-2025-46191 is a critical vulnerability in n/a, published on 9 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Arbitrary File Upload in user_payment_update.php in SourceCodester Client Database Management System 1.0 allows unauthenticated users to upload arbitrary files via the uploaded_file_cancelled field. Due to the absence of proper file extension checks, MIME type validation, and authentication, attackers can upload executable PHP files to a web-accessible directory (/files/). This allows them to execute arbitrary commands remotely by accessing the uploaded script, resulting in full Remote Code Execution (RCE) without authentication.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Lerouxyxchire Client Database Management System.

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

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

## Is CVE-2025-46191 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-46188](https://insights.sbomify.com/CVE-2025-46188/): SQL injection in n/a (critical 9.8)
- [CVE-2025-46189](https://insights.sbomify.com/CVE-2025-46189/): SQL injection in n/a (critical 9.8)
- [CVE-2025-46190](https://insights.sbomify.com/CVE-2025-46190/): SQL injection in n/a (critical 9.8)
- [CVE-2025-46192](https://insights.sbomify.com/CVE-2025-46192/): SQL injection in n/a (critical 9.8)
- [CVE-2025-46193](https://insights.sbomify.com/CVE-2025-46193/): File upload in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-46191 is a critical vulnerability in n/a, published on 9 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-46191 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-46191/ (Markdown: https://insights.sbomify.com/CVE-2025-46191/index.md)
```

## Sources

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

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