CVE-2023-31472: An issue was discovered on GL.iNet devices before 3.216.
Noroxi assessment
Priority: Monitor (action score 36/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: 19.8% (FIRST EPSS); higher than 97.4% of all records.
- Anyone who can reach it over the internet 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 GL.iNet devices before 3.216. There is an arbitrary file write in which an empty file can be created anywhere on the filesystem. This is caused by a command injection vulnerability with a filter applied.
- Published
- May 9, 2023
- Updated
- Jun 17, 2026
- EPSS
- 19.8% · 97th percentile
- CWE
- CWE-770
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 6 / 30 · 19.8%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
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 | gl-s20 firmware | cpe:2.3:o:gl-inet:gl-s20_firmware |
| gl-inet | gl-s20 | cpe:2.3:h:gl-inet:gl-s20 |
| gl-inet | gl-x3000 firmware | cpe:2.3:o:gl-inet:gl-x3000_firmware |
| gl-inet | gl-x3000 | cpe:2.3:h:gl-inet:gl-x3000 |
| gl-inet | gl-mt3000 firmware | cpe:2.3:o:gl-inet:gl-mt3000_firmware |
| gl-inet | gl-mt3000 | cpe:2.3:h:gl-inet:gl-mt3000 |
| gl-inet | gl-mt2500 firmware | cpe:2.3:o:gl-inet:gl-mt2500_firmware |
| gl-inet | gl-mt2500 | cpe:2.3:h:gl-inet:gl-mt2500 |
| gl-inet | gl-mt2500a firmware | cpe:2.3:o:gl-inet:gl-mt2500a_firmware |
| gl-inet | gl-mt2500a | cpe:2.3:h:gl-inet:gl-mt2500a |
| gl-inet | gl-axt1800 firmware | cpe:2.3:o:gl-inet:gl-axt1800_firmware |
| gl-inet | gl-axt1800 | cpe:2.3:h:gl-inet:gl-axt1800 |
and 52 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- gl-inet gl-a1300 firmwarebefore 3.216
- gl-inet gl-ap1300 firmwarebefore 3.216
- gl-inet gl-ap1300lte firmwarebefore 3.216
- gl-inet gl-ar300m firmwarebefore 3.216
- gl-inet gl-ar750 firmwarebefore 3.216
- gl-inet gl-ar750s firmwarebefore 3.216
- gl-inet gl-ax1800 firmwarebefore 3.216
- gl-inet gl-axt1800 firmwarebefore 3.216
- gl-inet gl-b1300 firmwarebefore 3.216
- gl-inet gl-b2200 firmwarebefore 3.216
- gl-inet gl-e750 firmwarebefore 3.216
- gl-inet gl-mifi firmwarebefore 3.216
- gl-inet gl-mt1300 firmwarebefore 3.216
- gl-inet gl-mt2500 firmwarebefore 3.216
- gl-inet gl-mt2500a firmwarebefore 3.216
- gl-inet gl-mt3000 firmwarebefore 3.216
- gl-inet gl-mt300n-v2 firmwarebefore 3.216
- gl-inet gl-mv1000 firmwarebefore 3.216
- gl-inet gl-mv1000w firmwarebefore 3.216
- gl-inet gl-s10 firmwarebefore 3.216
Same product
gl-inet: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-31475An issue was discovered on GL.iNet devices before 3.216.43Plan
- CVE-2023-31471An issue was discovered on GL.iNet devices before 3.216.39Monitor
- CVE-2023-31478An issue was discovered on GL.iNet devices before 3.216.39Monitor
Published before and after this one in the same product
- Later →CVE-2023-31474May 9, 2023 · An issue was discovered on GL.iNet devices before 3.216.30Monitor
- Later →CVE-2023-31477May 10, 2023 · A path traversal issue was discovered on GL.iNet devices before 3.216.30Monitor
- Later →CVE-2023-31473May 11, 2023 · An issue was discovered on GL.iNet devices before 3.216.20Monitor
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
- Anyone who can reach it over the internet 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
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-770 · Allocation of Resources Without Limits or ThrottlingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
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)
- FloodingCAPEC-125likelihood: High · Medium
- Excessive AllocationCAPEC-130likelihood: Medium · Medium
- XML Ping of the DeathCAPEC-147likelihood: Low · Medium
- Exponential Data ExpansionCAPEC-197likelihood: High · Medium
- Serialized Data Parameter BlowupCAPEC-229likelihood: High · High
- Serialized Data with Nested PayloadsCAPEC-230likelihood: Medium · High
- Oversized Serialized Data PayloadsCAPEC-231likelihood: Medium · High
- HTTP DoSCAPEC-469Low
ATT&CK techniques
- Network Denial of Service:Direct Network FloodT1498.001
- Network Denial of Service:Reflection AmplificationT1498.002
- Endpoint Denial of ServiceT1499
- Endpoint Denial of Service: OS Exhaustion FloodT1499.001
- Endpoint Denial of Service:Service Exhaustion FloodT1499.002
- Endpoint Denial of Service:Application Exhaustion FloodT1499.003
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.