VulnerabilityPublished 24 Jun 2024Updated 2 Aug 2024

CVE-2024-38892: Exposure of Sensitive Information Through Data Queries

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-38892, organizations should implement the following specific measures: 1) Immediately restrict access to the device’s management interfaces, ensuring they are not exposed to untrusted networks or the internet. 2) Segment networks to isolate vulnerable devices and limit attacker lateral movement opportunities. 3) Disable or restrict the ExportAllSettings.sh functionality if possible, or monitor and log all invocations of configuration export features to detect suspicious activity. 4) Apply strict access control lists (ACLs) and network-level protections to prevent unauthorized local network access. 5) Regularly audit device configurations and firmware versions to identify vulnerable devices. 6) Engage with Wavlink support or vendor channels to obtain patches or firmware updates as they become available. 7) Educate users about the risks of connecting to untrusted networks where attackers could exploit this vulnerability. 8) Employ network intrusion detection systems (NIDS) tuned to detect unusual requests to configuration export endpoints. These targeted actions go beyond generic advice by focusing on limiting network exposure, monitoring specific vulnerable functionality, and preparing for vendor updates.

Description

An issue in Wavlink WN551K1 allows a remote attacker to obtain sensitive information via the ExportAllSettings.sh component.

Impact

The primary impact of CVE-2024-38892 is the unauthorized disclosure of sensitive configuration information from affected Wavlink WN551K1 devices. This can lead to significant confidentiality breaches, exposing network credentials, administrative passwords, and other critical settings. Attackers gaining such information could leverage it to perform further network intrusions, lateral movement, or persistent access within an organization’s network. Although the vulnerability does not directly affect system integrity or availability, the exposure of sensitive data can indirectly compromise overall security posture. Organizations relying on these devices, especially in small office/home office environments, may face increased risk of targeted attacks or espionage. The requirement for network adjacency limits remote exploitation to attackers with local network access or those able to connect to the same Wi-Fi network, somewhat reducing the attack surface but not eliminating it. The absence of known exploits in the wild currently lowers immediate risk but does not preclude future exploitation.

CWE-202Exposure of Sensitive Information Through Data Queries (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
When trying to keep information confidential, an attacker can often infer some of the information by using statistics.
Architecture and Design
This is a complex topic. See the for a good discussion of best practices.
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/s4ndw1ch136/IOT-vuln-reports/blob/main/Wavlink/WN551K1/ExportLogs.sh/README.md (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 05:38 UTC

WeaknessesCWE-202

Technical details

References

Community reviews

Related threats