CVE-2024-45259: An issue was discovered on certain GL-iNet devices, including MT6000, MT3000, MT2500, AXT1800, and AX1800 4.6.2.
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An issue was discovered on certain GL-iNet devices, including MT6000, MT3000, MT2500, AXT1800, and AX1800 4.6.2. By intercepting an HTTP request and changing the filename property in the download interface, any file on the device can be deleted.
- Published
- Oct 24, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- CWE-326
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| gl-inet | mt3000 firmware | cpe:2.3:o:gl-inet:mt3000_firmware |
| gl-inet | gl-mt3000 | cpe:2.3:h:gl-inet:gl-mt3000 |
| gl-inet | mt2500 firmware | cpe:2.3:o:gl-inet:mt2500_firmware |
| gl-inet | mt2500 | cpe:2.3:h:gl-inet:mt2500 |
| gl-inet | axt1800 firmware | cpe:2.3:o:gl-inet:axt1800_firmware |
| gl-inet | axt1800 | cpe:2.3:h:gl-inet:axt1800 |
| gl-inet | ax1800 firmware | cpe:2.3:o:gl-inet:ax1800_firmware |
| gl-inet | ax1800 | cpe:2.3:h:gl-inet:ax1800 |
| gl-inet | b3000 firmware | cpe:2.3:o:gl-inet:b3000_firmware |
| gl-inet | b3000 | cpe:2.3:h:gl-inet:b3000 |
| gl-inet | a1300 firmware | cpe:2.3:o:gl-inet:a1300_firmware |
| gl-inet | a1300 | cpe:2.3:h:gl-inet:a1300 |
and 30 more
Check your site's encryption
This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.
Run the SSL checkAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- gl-inet a1300 firmware4.5.17
- gl-inet ar300m firmware4.3.17
- gl-inet ar300m16 firmware4.3.17
- gl-inet ar750 firmware4.3.17
- gl-inet ar750s firmware4.3.17
- gl-inet ax1800 firmware4.6.2 and later · before 4.6.4
- gl-inet axt1800 firmware4.6.2 and later · before 4.6.4
- gl-inet b1300 firmware4.3.17
- gl-inet b3000 firmware4.5.18
- gl-inet e750 firmware4.3.17
- gl-inet mt1300 firmware4.3.18
- gl-inet mt2500 firmware4.6.2 and later · before 4.6.4
- gl-inet mt3000 firmware4.6.2
- gl-inet mt300n-v2 firmware4.3.17
- gl-inet mt6000 firmware4.6.2
- gl-inet sft1200 firmware4.3.18
- gl-inet x3000 firmware4.4.9
- gl-inet x300b firmware4.5.17
- gl-inet x750 firmware4.3.18
- gl-inet xe300 firmware4.3.17
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-326 · Inadequate Encryption StrengthCVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.