CVE-2024-39227Public exploitNetwork attack vector

Unauthenticated code execution via unsanitized glc object path

Published Aug 6, 2024 · Updated Aug 15, 2024

Access-control failure in /cgi-bin/glc in listed GL.iNet router firmware allows remote attackers to execute code through crafted JSON. The glc binary accepts traversal sequences in the JSON object field and resolves attacker-chosen shared-library paths and methods without sanitization. No authentication is required to invoke the HTTP endpoint, enabling system commands that can manipulate the router.

CVSS severity9.8
Critical
EPSS probability1.19%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Access-control failure in /cgi-bin/glc in listed GL.iNet router firmware allows remote attackers to execute code through crafted JSON. The glc binary accepts traversal sequences in the JSON object field and resolves attacker-chosen shared-library paths and methods without sanitization. No authentication is required to invoke the HTTP endpoint, enabling system commands that can manipulate the router.

The record

CVE
CVE-2024-39227
Published
Aug 6, 2024
Updated
Aug 15, 2024
Vendor
GL.iNet
Product
GL-AR300M
Classifications
CWE-75, CWE-74, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 6, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 15, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4.3.11

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

GL.iNet · GL-AR300Mversion=4.3.11
GL.iNet · GL-MT1300version=4.3.11
GL.iNet · Puli AX (GL-XE3000)version=4.4
GL.iNet · GL-SFT1200version=4.3.11
GL.iNet · GL-MT3000version=4.5.16
GL.iNet · GL-AX1800version=4.5.16
GL.iNet · GL-XE300version=4.3.16
GL.iNet · GL-X750version=4.3.11
GL.iNet · GL-A1300version=4.5.16
GL.iNet · GL-X3000version=4.4
GL.iNet · GL-X300Bversion=4.5.16
GL.iNet · GL-AR750version=4.3.11
GL.iNet · GL-AR750Sversion=4.3.11
GL.iNet · GL-E750version=4.3.12
GL.iNet · GL-B1300version=4.3.11
GL.iNet · GL-S1300version=4.3.13
GL.iNet · GL-MT2500version=4.5.16
GL.iNet · GL-AXT1800version=4.5.16
GL.iNet · GL-AP1300version=4.3.13
GL.iNet · GL-AR300M16version=4.3.11

Published CVSS scores

9.8CISA-ADPCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
9.8NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-75Failure to Sanitize Special Elements into a Different Plane (Special Element Injection)
CWE-74Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo