CVE-2024-39150VulnerabilityPublished 5 Jul 2024Updated 13 Nov 2024

CVE-2024-39150: vditor · n/a

Affects vditorSource CVE Database V5

Not known to be exploited · CVSS 5.9 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

5.9Medium

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

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

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

Attack Vector: Network
Attack Complexity: High
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: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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 5 Jul 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 2026-10-26.

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 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

Affected software

Product	Affected	Fixed in
npmvditor`pkg:npm/vditor`Other threats	Affected <=3.9.8	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official patch is released, organizations should implement the following specific mitigations: 1) Restrict network access to vditor instances by using firewalls or network segmentation to limit exposure to trusted users only. 2) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious crafted data packets targeting vditor. 3) Monitor application logs and network traffic for unusual or malformed packets that could indicate exploitation attempts. 4) Conduct code reviews and apply temporary input validation or sanitization measures if possible, to mitigate arbitrary file read vectors. 5) Prepare for rapid deployment of patches once available by maintaining an inventory of affected vditor deployments. 6) Educate development and operations teams about the vulnerability to ensure timely response. 7) Consider isolating or disabling vditor components where feasible until the vulnerability is addressed. These targeted actions go beyond generic advice by focusing on network-level controls and proactive monitoring specific to the nature of the vulnerability.

Description

vditor v.3.9.8 and before is vulnerable to Arbitrary file read via a crafted data packet.

Impact

The primary impact of CVE-2024-39150 is unauthorized disclosure of sensitive information due to arbitrary file read capabilities. Attackers can potentially access configuration files, credentials, or other sensitive data stored on systems running vulnerable versions of vditor. This can lead to further compromise if attackers leverage the disclosed information for lateral movement or privilege escalation. Since the vulnerability does not affect integrity or availability, it does not directly enable data modification or service disruption. However, the confidentiality breach alone can have serious consequences, especially in environments handling sensitive or regulated data. The medium severity score reflects the balance between the potential impact and the high complexity required for exploitation. Organizations with internet-facing vditor instances or those integrated into critical workflows are at higher risk. The absence of known exploits reduces immediate threat but does not eliminate the risk of future exploitation.

References

b3log.org/vditor/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 04:17 UTC

Technical details

References

Community reviews

Related threats