# CVE-2024-23762: File upload in n/a

> Attackers can execute arbitrary code by uploading a crafted PHP file via the unrestricted file upload vulnerability in the Content Manager feature.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2024
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-9h2p-2c35-fq37

## What is CVE-2024-23762?

CVE-2024-23762 is a high-severity vulnerability in n/a, published on 12 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unrestricted File Upload vulnerability in Content Manager feature in Gambio 4.9.2.0 allows attackers to execute arbitrary code via upload of crafted PHP file.

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

## Which versions are affected by CVE-2024-23762?

It affects 1 product.


Products: Gambio Gambio.

## How do I fix CVE-2024-23762?

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

## Is CVE-2024-23762 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-23759](https://insights.sbomify.com/CVE-2024-23759/): Deserialization in n/a (critical 9.8)
- [CVE-2024-23761](https://insights.sbomify.com/CVE-2024-23761/): Code injection in n/a (critical 9.8)
- [CVE-2024-23763](https://insights.sbomify.com/CVE-2024-23763/): SQL injection in n/a (critical 9.8)
- [CVE-2024-23760](https://insights.sbomify.com/CVE-2024-23760/): Information disclosure in n/a (low 2.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-23762 and fix it if it is affected.

What it is: CVE-2024-23762 is a high-severity vulnerability in n/a, published on 12 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-23762 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-2024-23762/ (Markdown: https://insights.sbomify.com/CVE-2024-23762/index.md)
```

## Sources

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

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