dbcve.org
InjectionWeakness · CWE-74

CVE-2026-11447

MEDIUM · 6.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 →
69/100
Remediation priority · Elevated
Remotely reachable 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 security flaw has been discovered in GL.iNet GL-MT3000 up to 4.4.5. Impacted is the function iwinfo_backend of the file iwinfo.so of the component MTK Backend. The manipulation of the argument device results in command injection. The attack can be executed remotely. The exploit has been released to the public and may be used for attacks. Upgrading to version 4.7 is recommended to address this issue. Upgrading the affected component is recommended. The vendor confirms: "Starting from version 4.7, SDK has added global protection to intercept malicious injection".

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

Command injection vulnerability in GL.iNet GL-MT3000 routers allows remote attackers to execute arbitrary commands via the device argument in the iwinfo_backend function of the iwinfo.so library in the MTK Backend component. The vulnerability affects firmware versions up to 4.4.5.

MitigationUpgrade GL-MT3000 firmware to version 4.7 or later, which includes global protection to intercept malicious injection attempts.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 router model
    Check the device label or access the web admin panel (typically at 192.168.8.1) and look for the model name in the top-right corner or System > Device Info page
    Affected if The device is not a GL-MT3000, then it is not affected by this specific CVE
  2. Check the installed firmware version
    In the web admin panel, go to System > Upgrade or System > Device Info to view the current firmware version; alternatively, run 'cat /etc/gl-version' via SSH
    Affected if The firmware version is 4.4.5 or lower, indicating the device falls within the vulnerable version range
  3. Verify the iwinfo backend component is present
    Run 'ls -la /usr/lib/iwinfo/' via SSH to list the iwinfo library files; check for the existence of 'iwinfo.so'
    Affected if The iwinfo.so library file exists, meaning the vulnerable MTK Backend component is loaded on the device
  4. Confirm management interface is network-accessible
    Check if the router's web admin or SSH interface is exposed to untrusted networks (WAN) by reviewing Firewall settings in the web panel or running 'iptables -L -n' via SSH
    Affected if The management interface (port 80/443 for web or 22 for SSH) is listening on WAN or accessible from untrusted networks, increasing exposure to remote exploitation

A GL-MT3000 router running firmware version 4.4.5 or lower with the iwinfo.so component present and its management interface exposed to the network is likely affected by CVE-2026-11447.

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.7 or later, which includes global protection to intercept malicious injection attempts.

Recommended fix High confidence

GL.iNet GL-MT3000 firmware version 4.7

  1. 1. Obtain the firmware version 4.7 for GL.iNet GL-MT3000 from the official vendor website
  2. 2. Access the router's web administration interface or CLI
  3. 3. Navigate to the firmware upgrade section
  4. 4. Upload and apply the version 4.7 firmware
  5. 5. After reboot, verify the firmware version has been updated to 4.7 or later
  6. 6. Confirm the iwinfo.so component has been updated as part of the firmware upgrade

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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