# CVE-2026-37748: File upload in n/a

> An authenticated admin can upload a PHP webshell to achieve Remote Code Execution due to missing file validation in the Visitor Management System.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2026
- **Updated:** 21 Apr 2026
- **Also known as:** GHSA-3pw2-2fp4-54wm

## What is CVE-2026-37748?

CVE-2026-37748 is a high-severity vulnerability in n/a, published on 21 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Visitor Management System 1.0 by sanjay1313 is vulnerable to Unrestricted File Upload in vms/php/admin_user_insert.php and vms/php/update_1.php. The move_uploaded_file() function is called without any MIME type, extension, or content validation, allowing an authenticated admin to upload a PHP webshell and achieve Remote Code Execution on the server.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2026-37748?

It affects 1 product.


Products: Sanjay1313 Visitor Management System.

## How do I fix CVE-2026-37748?

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

## Is CVE-2026-37748 being exploited?

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

Public exploit code:

- Visitor Management System 1.0 - Unrestricted File Upload → RCE (CVE-2026-37748) (github_poc): https://github.com/menevarad007/CVE-2026-37748

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-37748 and fix it if it is affected.

What it is: CVE-2026-37748 is a high-severity vulnerability in n/a, published on 21 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-37748 exists.

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

## Sources

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

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