CVE-2024-27626: Dotclear · Cross-site Scripting
Source CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Mar 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.
What to do
AI-suggested
To mitigate CVE-2024-27626, organizations should first verify if an official patch or update from Dotclear is available and apply it promptly. In the absence of a patch, administrators should implement strict input validation and output encoding on all user-supplied data in the admin panel’s search functionality to prevent script injection. Employing a Content Security Policy (CSP) with directives that restrict script execution sources can reduce the impact of potential XSS payloads. Administrators should be trained to recognize suspicious URLs and avoid clicking untrusted links, especially those targeting the admin interface. Additionally, enabling multi-factor authentication (MFA) for admin accounts can reduce the risk of session hijacking. Regular security audits and monitoring of admin panel access logs can help detect suspicious activities. Finally, isolating the admin panel behind VPNs or IP whitelisting can limit exposure to external attackers.
Description
A Reflected Cross-Site Scripting (XSS) vulnerability has been identified in Dotclear version 2.29. The flaw exists within the Search functionality of the Admin Panel.