CVE-2023-50919 is an authentication bypass vulnerability affecting multiple GL.iNet devices before firmware version 4.5.0. The issue is in the NGINX authentication logic, where Lua string pattern matching is used in a way that allows authentication checks to be bypassed. Affected versions explicitly include A1300 4.4.6, AX1800 4.4.6, AXT1800 4.4.6, MT3000 4.4.6, MT2500 4.4.6, MT6000 4.5.0, MT1300 4.3.7, MT300N-V2 4.3.7, AR750S 4.3.7, AR750 4.3.7, AR300M 4.3.7, and B1300 4.3.7. Based on the available information, the flaw permits requests to satisfy or evade intended authentication enforcement due to improper use of Lua pattern matching within NGINX request handling.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (Ruby file) that exploits an unauthenticated remote command execution vulnerability (CVE-2023-50445) in multiple GL.iNet network devices. The exploit targets the JSON-RPC API exposed by the device's web management interface (typically at /rpc over HTTPS, port 443). It leverages a command injection flaw in the 'logread' module, specifically via the 'gl_system_log' and 'gl_crash_log' interfaces. The exploit can be used after obtaining a valid Admin-Token session ID (SID), which itself can be acquired by chaining with CVE-2023-50919 (authentication bypass via SQL injection). The module supports both direct command execution and deployment of Meterpreter reverse shells, with options for various architectures (MIPS, ARM, AARCH64). The code is weaponized, allowing for easy payload customization and reliable exploitation. The repository is structured as a single Metasploit module file, with all logic and payload handling contained within.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.