CVE-2024-34449VulnerabilityPublished 3 May 2024Updated 2 Aug 2024

CVE-2024-34449: vditor · n/a

Affects vditorSource CVE Database V5

Not known to be exploited : upgrade to 3.10.3 when convenient.

Data as of 26 Oct 2026, 08:30 UTC

Severity

Medium

Rated Medium by the CNA (mitre) · No CVSS score from NVD or the CNA

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

Exploitation evidence

Disclosed: evidence found.
CVE published 3 May 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 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

Upgrade vanessa219/vditor to 3.10.3.

Affected software

Product	Affected	Fixed in
GitHubvanessa219/vditor`pkg:github/vanessa219/vditor`Other threats	Affected <3.10.3	Fixed in 3.10.3

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

AI-suggested

Upgrade to Vditor version 3.10.3 or later, where the vulnerability is fixed. Alternatively, ensure that the sanitize=true option is enabled as per the vendor's guidance to mitigate the vulnerability.

Description

Vditor version prior to 3.10.3 contains a cross-site scripting (XSS) vulnerability via an attribute of an anchor (A) element. The vendor recommends mitigating this issue by enabling the sanitize=true option. The vulnerability is fixed in version 3.10.3.

Impact

Successful exploitation could allow an attacker to execute arbitrary scripts in the context of the affected application, potentially leading to session hijacking, defacement, or other client-side attacks. However, the vendor's recommended mitigation (sanitize=true) reduces this risk. No known exploits in the wild have been reported.

Summary

CVE-2024-34449 is a cross-site scripting vulnerability in Vditor before version 3.10.3. It arises from improper handling of attributes in anchor elements, allowing injection of malicious scripts. The vendor advises users to mitigate the risk by setting sanitize=true, which presumably sanitizes input to prevent XSS. The vulnerability is addressed in Vditor 3.10.3, which includes the fix.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Oct 2026, 21:14 UTC

Technical details

References

Community reviews

Related threats