Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-18613 – Unauthenticated Remote Code Execution – GL.iNet GL-MT3000 firmware 4.4.0 through 4.

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-18613 is an unauthenticated injection vulnerability in the GL.iNet GL-MT3000 (Beryl AX) router. The plugins.set_config method exposed by the plugins.so native plugin at the /cgi-bin/glc endpoint fails to neutralize attacker-supplied input, allowing a remote, unauthenticated attacker to inject a malicious software feed source and ultimately achieve remote code execution as root. The issue is rated critical.

Technical details

  • Root cause: The plugins.set_config method (served by /usr/lib/oui-httpd/rpc/plugins.so via the /cgi-bin/glc endpoint) writes user-supplied opkg feed sources to /etc/opkg/customfeeds.conf without validating the URL scheme, verifying the domain, filtering shell metacharacters, or enforcing authentication (CWE-74 / CWE-707, improper neutralization / injection).
  • Trigger conditions: An attacker sends an unauthenticated HTTP POST to /cgi-bin/glc with a JSON payload invoking object: plugins, method: set_config, supplying attacker-controlled name and url feed entries. No session, credentials, or user interaction are required.
  • Attack vector: Network. The endpoint is reachable and exploitable remotely with no authentication.
  • Impact: The injected feed enables a chain of update_repository followed by install_package, installing an attacker-controlled package whose preinst/postinst scripts execute as root — resulting in full device compromise (confidentiality, integrity, and availability all impacted).

Affected software

  • GL.iNet GL-MT3000 (Beryl AX) firmware versions 4.4.0, 4.4.1, 4.4.2, 4.4.3, 4.4.4, and 4.4.5.

Severity

  • CVSS v3.1 base score: 9.8 (Critical) — vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
  • CVSS v4.0 base score: 9.3 (Critical) — vector CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N.

Mitigation and recommended actions

  • Immediate: Upgrade GL-MT3000 devices to a vendor firmware release later than 4.4.5 as soon as a fixed build is available from GL.iNet, and monitor the GL.iNet security advisories for the corrected version.
  • If no patch: Do not expose the router’s web/management interface (including /cgi-bin/glc) to the internet or untrusted networks. Restrict administrative access to trusted management segments or VPN, block inbound access to the HTTP management port at the network edge, and monitor for unexpected requests to /cgi-bin/glc and unexpected changes to /etc/opkg/customfeeds.conf.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: GL.iNet, GL-MT3000, Beryl AX, GL.iNet Admin Panel

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge