dbcve.org
InjectionWeakness · CWE-74

CVE-2026-11452

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 vulnerability has been found in GL.iNet GL-MT3000 up to 4.4.5. Affected is the function FUN_0042e200 of the file /cgi-bin/glc of the component SET_USER_PWD Handler. The manipulation of the argument Password leads to command injection. The attack can be initiated remotely. Upgrading to version 4.8.1 is able to address this issue. The affected component should be upgraded. The vendor explains: " The current code escapes single quotes in the password parameter and handles it inside a shell single‑quote context. The payloads in the report, which rely on $() or backticks to trigger command substitution, are not executed under the current code path. We tested on a GL‑MT3000 device running firmware 4.8.1 using similar payloads, and no command‑execution marker file was created."

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 · moderate confidence

Command injection vulnerability in GL.iNet GL-MT3000 routers (firmware up to 4.4.5) in the SET_USER_PWD handler of /cgi-bin/glc. The Password parameter is not properly sanitized before being passed to a shell execution context, allowing remote authenticated attackers to inject arbitrary shell commands.

MitigationUpgrade router firmware to version 4.8.1 or later, which implements proper single-quote escaping and handles the password parameter within a shell single-quote context to prevent command substitution payloads.

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 router model
    Check if the device is a GL.iNet GL-MT3000 router by examining the device label, web interface, or via SSH run: cat /proc/cpuinfo or ifconfig to observe network interfaces
    Affected if The device is a GL-MT3000 model
  2. Check firmware version
    Access the router web interface and look for the firmware version in System > Settings > Firmware Version, or via SSH run: cat /etc/os-release or nvram get firmware_version
    Affected if The firmware version is 4.4.5 or lower (or any version below 4.8.1)
  3. Verify the CGI binary exists
    Via SSH, check if /cgi-bin/glc exists: ls -la /www/cgi-bin/glc or test -f /usr/bin/glc
    Affected if The vulnerable CGI binary is present on the device
  4. Test if SET_USER_PWD handler is accessible
    Attempt to access the endpoint via HTTP POST to http://<router-ip>/cgi-bin/glc with a request containing the SET_USER_PWD action parameter; or examine if the web interface exposes user password change functionality
    Affected if The SET_USER_PWD handler is exposed and accepts user-controlled Password parameter input

The device is affected if it is a GL-MT3000 router running firmware version 4.4.5 or below with the /cgi-bin/glc CGI endpoint and SET_USER_PWD functionality accessible.

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 router firmware to version 4.8.1 or later, which implements proper single-quote escaping and handles the password parameter within a shell single-quote context to prevent command substitution payloads.

Recommended fix High confidence

4.8.1

  1. Download firmware version 4.8.1 from the official GL.iNet support website (support.glinet.com)
  2. Access the GL-MT3000 router's web administration interface
  3. Navigate to System > Firmware Upgrade or similar section
  4. Upload the 4.8.1 firmware file and apply the update
  5. Allow the device to reboot and complete the upgrade process
  6. 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
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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