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

> Attackers can upload arbitrary files to GL-iNet routers, leading to information leakage and complete device control.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Oct 2024
- **Updated:** 28 Oct 2024
- **Also known as:** GHSA-vpfw-56r4-6hcq

## What is CVE-2024-45263?

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

### Official description

An issue was discovered on certain GL-iNet devices, including MT6000, MT3000, MT2500, AXT1800, and AX1800 4.6.2. The upload interface allows the uploading of arbitrary files to the device. Once the device executes the files, it can lead to information leakage, enabling complete control.

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

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

It affects 21 products.


Products: Gl-Inet A1300 Firmware, Gl-Inet Ar300m16 Firmware, Gl-Inet Ar300m Firmware, Gl-Inet Ar750 Firmware, Gl-Inet Ar750s Firmware, Gl-Inet Ax1800 Firmware, Gl-Inet Axt1800 Firmware, Gl-Inet B1300 Firmware, Gl-Inet B3000 Firmware, Gl-Inet E750 Firmware, Gl-Inet Mt1300 Firmware, Gl-Inet Mt2500 Firmware, Gl-Inet Mt3000 Firmware, Gl-Inet Mt300n-V2 Firmware, Gl-Inet Mt6000 Firmware, Gl-Inet Sft1200 Firmware, Gl-Inet X3000 Firmware, Gl-Inet X300b Firmware, Gl-Inet X750 Firmware, Gl-Inet Xe3000 Firmware and 1 more.

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

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

## Is CVE-2024-45263 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-39225](https://insights.sbomify.com/CVE-2024-39225/): Other in n/a (critical 9.8)
- [CVE-2024-39227](https://insights.sbomify.com/CVE-2024-39227/): Command injection in n/a (critical 9.8)
- [CVE-2024-39228](https://insights.sbomify.com/CVE-2024-39228/): Command injection in n/a (critical 9.8)
- [CVE-2024-45262](https://insights.sbomify.com/CVE-2024-45262/): Path traversal in n/a (high 8.8)
- [CVE-2024-45260](https://insights.sbomify.com/CVE-2024-45260/): Missing authorization in n/a (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45263 is a high-severity vulnerability in n/a, published on 24 Oct 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-45263 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-45263/ (Markdown: https://insights.sbomify.com/CVE-2024-45263/index.md)
```

## Sources

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

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