dbcve.org
Mt6000 FirmwareOperating system · Gl Inet

CVE-2024-45263

HIGH · 8.8 CVSS v3.1 Published 2024-10-24
Fix available
A fix is available. Upgrade to 4.6.4 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The web-based upload interface on GL-iNet MT6000, MT3000, MT2500, AXT1800, and AX1800 devices (firmware 4.6.2) lacks proper validation of uploaded files, allowing authenticated attackers to upload and execute arbitrary files. This leads to information leakage and complete device compromise.

MitigationRestrict access to the administrative upload interface, implement strict file type validation and content inspection before storage, and apply vendor firmware updates when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mt6000 FirmwareOperating system
Affected:= 4.6.2
Mt3000 FirmwareOperating system
Affected:>= 4.6.2, < 4.6.4
Mt2500 FirmwareOperating system
Affected:>= 4.6.2, < 4.6.4
Axt1800 FirmwareOperating system
Affected:>= 4.6.2, < 4.6.4
Ax1800 FirmwareOperating system
Affected:>= 4.6.2, < 4.6.4
B3000 FirmwareOperating system
Affected:= 4.5.18
A1300 FirmwareOperating system
Affected:= 4.5.17
X300b FirmwareOperating system
Affected:= 4.5.17

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model and firmware version
    Log into the router admin web interface and navigate to System > Firmware or check the status page. Alternatively, run 'cat /etc/glversion' or 'ubus call system board' via SSH.
    Affected if Device is MT6000 (firmware 4.6.2), MT3000/MT2500/AXT1800/AX1800 (firmware >= 4.6.2 and < 4.6.4), B3000 (firmware 4.5.18), A1300 (firmware 4.5.17), or X300b (firmware 4.5.17)
  2. Verify web admin interface is accessible
    Attempt to access the router's web interface at its LAN or WAN IP address (https://<router_ip>). Check if the login page loads.
    Affected if The web admin interface is reachable (this is where the vulnerable upload function exists)
  3. Check if file upload functionality is enabled
    Log into the router web interface and look for upload features in sections like Firmware Upgrade, Backup/Restore, or Application uploads.
    Affected if Any file upload or firmware upgrade interface is present and enabled on the device
  4. Inspect web directories for unexpected files
    Via SSH, list contents of /www, /www/cgi-bin, or /tmp. Look for unfamiliar .php, .sh, or binary files that were not part of the official firmware.
    Affected if Unexpected script or executable files exist in web directories, suggesting possible exploitation
  5. Review system logs for upload-related events
    Check router logs via the web interface (Status > Logs) or by reading /var/log/messages. Look for upload.cgi or file upload API calls.
    Affected if Logs show suspicious file upload requests or unauthorized firmware upload attempts

The device is affected if it matches one of the listed model/version combinations AND has the web-based upload interface accessible and enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.6.4 or later
Fixed in 4.6.4
Interim mitigation

Restrict access to the administrative upload interface, implement strict file type validation and content inspection before storage, and apply vendor firmware updates when available.

Recommended fix Moderate confidence

Firmware 4.6.4 or later for MT3000/MT2500/AXT1800/AX1800; latest available firmware for MT6000, B3000, A1300, X300b

  1. 1. Identify the exact GL-iNet device model from the affected list (MT6000, MT3000, MT2500, AXT1800, AX1800, B3000, A1300, X300b)
  2. 2. Navigate to the official GL-iNet support/download page: https://www.gl-inet.com/
  3. 3. Locate the firmware download section for your specific device model
  4. 4. Download firmware version 4.6.4 or later for MT3000, MT2500, AXT1800, AX1800 devices
  5. 5. For MT6000, download the latest available firmware version (later than 4.6.2)
  6. 6. For B3000, A1300, and X3000 devices, download the latest available firmware version (later than 4.5.18, 4.5.17 respectively)
  7. 7. Access the device web administration interface
  8. 8. Navigate to System > Firmware or similar firmware upgrade section
Caveat Review release notes for any configuration changes or feature modifications between versions; backup device configuration before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mt6000 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45263 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-45263 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data