CVE-2026-18613 GL-iNet CVE debrief

Who should care

Defenders responsible for GL-iNet GL-MT3000 devices, particularly those running firmware up to 4.4.5, should assess exposure and verify the effectiveness of current security controls.

Why it matters

Defenders should prioritize verifying exposure of GL-iNet GL-MT3000 devices running firmware up to 4.4.5 and assess the effectiveness of current security controls due to the potential for injection attacks.

• Verify exposure of GL-iNet GL-MT3000 devices running firmware up to 4.4.5
• Assess potential impact of injection attacks on device functionality and data
• Monitor for potential exploitation attempts

Technical summary

The vulnerability affects the plugins.set_config function of /cgi-bin/glc in GL-iNet GL-MT3000 up to 4.4.5, allowing for injection attacks. The attack can be launched remotely. Defenders should prioritize verifying exposure of GL-iNet GL-MT3000 devices running firmware up to 4.4.5 and assess the effectiveness of current security controls. This includes reviewing the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Planning vendor-supported updates or mitigations through normal change control where exposure is confirmed is also recommended.

Defensive priority

Defenders should prioritize verifying exposure of GL-iNet GL-MT3000 devices running firmware up to 4.4.5 and assess the effectiveness of current security controls.

Recommended defensive actions

• Verify exposure of GL-iNet GL-MT3000 devices running firmware up to 4.4.5
• Assess the effectiveness of current security controls
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. However, the scope of affected versions and potential impact require further verification from official sources. The CVE Program record (cve-org) and NVD detail page (nvd) offer source-provided CVE metadata and vulnerability assessments. Additional details may be found in source references (ref-3, ref-4, ref-5).

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.