# CVE-2026-38751: OpenSTAManager contains an arbitrary file upload vulnerability in its module update functionality

> Attackers can upload arbitrary files via the module update functionality, potentially leading to remote code execution.

- **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:** 4 May 2026
- **Updated:** 5 May 2026
- **Also known as:** GHSA-rm34-fg4m-39mw

## What is CVE-2026-38751?

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

### Official description

OpenSTAManager version 2.10 and earlier contains an arbitrary file upload vulnerability in the module update functionality (modules/aggiornamenti/upload_modules.php)

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

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

2 open source packages ship an affected version, including devcode-it/openstamanager. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `devcode-it/openstamanager` | Packagist | All versions to 2.10-beta | None |
| `devcode-it/openstamanager` | Packagist | All versions to 2.10-beta | None |

Products: Devcode Openstamanager.

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

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

## Is CVE-2026-38751 being exploited?

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

Public exploit code:

- OpenSTAManager-RCE-Exploit-CVE-2026-38751 (github_poc): https://github.com/b0ySie7e/OpenSTAManager-RCE-Exploit-CVE-2026-38751
- OpenSTAManager RCE Exploit (CVE-2026-38751) (github_poc): https://github.com/hackthem/OpenSTAManager_RCE_Exploit-CVE-2026-38751-
- https://github.com/Why-Shell/CVE-2026-38751 (github_poc): https://github.com/Why-Shell/CVE-2026-38751
- This repository contains a proof-of-concept (PoC) exploit for CVE-2026-38751, affecting OpenSTAManager ≤ 2.10.  The vulnerability allows an authenticated attacker to upload a malicious module via the module update functionality, leading to arbitrary file upload and remote code execution (RCE). (github_poc): https://github.com/Mkps/CVE-2026-38751-OpenSTAManager-Arbitrary-File-Upload-PoC
- Write-up машины Enigma (HTB). Корпоративная инфраструктура: NFS exposure → Webmail recon → OpenSTAManager RCE (CVE-2026-38751) → прескалация до root через Command Injection в OliveTin API. Полный гайд с скриншотами и объяснением логики. (github_poc): https://github.com/Wingleszy/HTB-Enigma-walkthrough

## Other vulnerabilities in n/a

- [CVE-2026-27012](https://insights.sbomify.com/CVE-2026-27012/): Unauthenticated privilege escalation in OpenSTAManager via modules/utenti/actions.php (critical 9.8)
- [CVE-2025-69212](https://insights.sbomify.com/CVE-2025-69212/): OpenSTAManager has an OS Command Injection in P7M File Processing (critical 9.4)
- [CVE-2026-35470](https://insights.sbomify.com/CVE-2026-35470/): OpenSTAManager has a SQL Injection via righe Parameter in confronta_righe Modals (high 8.8)
- [CVE-2026-28805](https://insights.sbomify.com/CVE-2026-28805/): OpenSTAManager: Time-Based Blind SQL Injection via `options[stato]` Parameter (high 8.8)
- [CVE-2026-35168](https://insights.sbomify.com/CVE-2026-35168/): OpenSTAManager: SQL Injection via Aggiornamenti Module (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-38751 is a high-severity vulnerability in n/a, published on 4 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-38751 in the wild and no public exploit code.

Affected packages and fixed versions:
- devcode-it/openstamanager (Packagist): affected all versions up to 2.10-beta; no fix listed
- devcode-it/openstamanager (Packagist): affected all versions up to 2.10-beta; no fix listed

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

## Sources

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

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