Code execution via uploaded crontab file
Published Jan 3, 2024 · Updated Jun 3, 2025
Remote code execution in GL.iNet router firmware through 4.5.0 allows remote attackers to run arbitrary code using a stolen AdminToken cookie. The /upload endpoint accepts attacker-controlled path data and file contents, allowing a crontab file to be placed in a directory processed by cron. Possession of the administrative session cookie is required; successful exploitation schedules attacker-supplied commands on the router.
Summary
What happened
Remote code execution in GL.iNet router firmware through 4.5.0 allows remote attackers to run arbitrary code using a stolen AdminToken cookie. The /upload endpoint accepts attacker-controlled path data and file contents, allowing a crontab file to be placed in a directory processed by cron. Possession of the administrative session cookie is required; successful exploitation schedules attacker-supplied commands on the router.
The record
- CVE
- CVE-2023-50922
- Published
- Jan 3, 2024
- Updated
- Jun 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-434, T1053.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 3, 2024CVE publishedPublication date reported by the CVE source.
- Jun 3, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Weakness, pattern, technique
Public exploit references
- GL.iNet gl_crontabs proof of conceptproof of concept · unverified
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