dbcve.org
InjectionWeakness · CWE-74

CVE-2026-11451

HIGH · 7.3 CVSS v3.1 Published 2026-06-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable 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
A flaw has been found in GL.iNet GL-MT3000 4.4.5. This impacts the function snprintf of the file /cgi-bin/glc of the component FTP Protocol Handler. Executing a manipulation of the argument media_dir can lead to command injection. It is possible to launch the attack remotely. Upgrading to version 4.8.1 will fix this issue. You should upgrade the affected component. The vendor explains: "In version 4.8.1, before writing media_dir to the FTP configuration command, the code escapes single quotes using escape_single_quote(). The payloads in the report—which rely on closing a single quote, appending commands with a semicolon, and commenting out the tail with #—cannot escape execution under the current code path. We also verified this on a GL‑MT3000 device running firmware version 4.8.1 using similar payloads calling the /NAS_API_SET_PROTO_CONFIG interface. Although the interface returned success, the marker file intended to prove command execution was not created; the payload was written into /etc/vsftpd.conf only as ordinary configuration content and did not trigger any shell command execution. Therefore, with the current firmware version and default runtime environment, we could not reproduce the claimed “unauthorized command injection in set_proto_config”."

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 GL-MT3000 router firmware versions prior to 4.8.1 contain a command injection vulnerability in the FTP Protocol Handler (/cgi-bin/glc). The media_dir parameter passed to the snprintf function is not properly sanitized, allowing attackers to inject shell commands by closing a single quote, appending commands with a semicolon, and using # to comment out the remainder of the configuration line.

MitigationUpgrade GL-MT3000 firmware to version 4.8.1 or later, which implements single-quote escaping via escape_single_quote() before writing media_dir to the FTP configuration.

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

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 the device model
    Access the router admin panel or run 'cat /proc/cpuinfo' or 'ubus call system board' to confirm the device is GL-MT3000
    Affected if Device is not GL-MT3000 (not affected)
  2. Check the installed firmware version
    Access router admin panel at System > Firmware or run 'cat /etc/os-release' or 'glbsp -v' to retrieve the firmware version
    Affected if Firmware version is prior to 4.8.1 (potentially affected)
  3. Verify FTP service configuration
    Check if FTP server is enabled via NAS_API_SET_PROTO_CONFIG or by inspecting /etc/config/freeradius or /tmp/fstab for FTP mount points, or via uci show ftp
    Affected if FTP protocol handler is not configured (not exploitable)
  4. Inspect the media_dir parameter handling
    If FTP is configured, examine the configuration files or API responses for the media_dir parameter in /cgi-bin/glc via NAS_API_SET_PROTO_CONFIG interface to see if quotes are escaped
    Affected if Single quotes in media_dir are not escaped (vulnerable)

Device is affected if it is a GL-MT3000 with firmware prior to 4.8.1 and has FTP protocol configured with unescaped single quotes in media_dir parameter.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade GL-MT3000 firmware to version 4.8.1 or later, which implements single-quote escaping via escape_single_quote() before writing media_dir to the FTP configuration.

Recommended fix High confidence

4.8.1

  1. Download firmware version 4.8.1 for GL-MT3000 from the official GL.iNet support website
  2. Access the GL-MT3000 router admin interface via web browser
  3. Navigate to the System settings or Firmware Upgrade section
  4. Upload the firmware version 4.8.1 file and apply the upgrade
  5. Verify the upgrade was successful by checking the firmware version in the admin interface

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11451 — 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-2026-11451 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