Skip to main content
CVE-2023-38944VulnerabilityPublished Updated

CVE-2023-38944: n/a

Source CVE Database V5

0

Not known to be exploited · 15% EPSS · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
15.5% chance of exploitation in 30 days – higher than 96% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Mar 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

AI-suggested

1. Immediately identify and inventory all Multilaser RE160V and RE163V routers running the vulnerable firmware versions within the network. 2. Restrict access to router management interfaces by implementing network segmentation and firewall rules that limit HTTP access to trusted administrative networks only. 3. Deploy intrusion detection/prevention systems (IDS/IPS) to monitor and alert on suspicious HTTP header modifications or unauthorized access attempts targeting router management interfaces. 4. Disable remote management features if not strictly necessary, or enforce VPN-based access with strong authentication for remote administration. 5. Regularly monitor vendor communications for firmware updates or patches addressing this vulnerability and apply them promptly once available. 6. Conduct security awareness training for network administrators to recognize signs of router compromise. 7. Consider replacing vulnerable devices with models from vendors with stronger security track records if patches are delayed or unavailable. 8. Implement network-level anomaly detection to identify unusual traffic patterns indicative of exploitation attempts. These measures go beyond generic advice by focusing on access control hardening, monitoring for specific attack vectors, and proactive device management.

Description

An issue in Multilaser RE160V firmware v12.03.01.09_pt and Multilaser RE163V firmware v12.03.01.10_pt allows attackers to bypass the access control and gain complete access to the application via modifying a HTTP header.

References

Community reviews

Loading reviews…