# CVE-2023-33253: File upload in n/a

> Authenticated low-privileged users can upload malicious PHP files to execute system commands due to insufficient file validation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2023
- **Updated:** 3 Jan 2025
- **Also known as:** GHSA-c5r4-m7mf-vx33

## What is CVE-2023-33253?

CVE-2023-33253 is a high-severity vulnerability in n/a, published on 12 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

LabCollector 6.0 though 6.15 allows remote code execution. An authenticated remote low-privileged user can upload an executable PHP file and execute system commands. The vulnerability is in the message function, and is due to insufficient validation of the file (such as shell.jpg.php.shell) being sent.

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

## Which versions are affected by CVE-2023-33253?

It affects 1 product.


Products: Agilebio Labcollector.

## How do I fix CVE-2023-33253?

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

## Is CVE-2023-33253 being exploited?

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

Public exploit code:

- https://github.com/Toxich4/CVE-2023-33253 (github_poc): https://github.com/Toxich4/CVE-2023-33253

## Other vulnerabilities in n/a

- [CVE-2019-25438](https://insights.sbomify.com/CVE-2019-25438/): LabCollector 5.423 SQL Injection via login.php (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-33253 and fix it if it is affected.

What it is: CVE-2023-33253 is a high-severity vulnerability in n/a, published on 12 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-33253 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-2023-33253/ (Markdown: https://insights.sbomify.com/CVE-2023-33253/index.md)
```

## Sources

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

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