CVE-2024-41351: bjyadmin · 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.3% chance of exploitation in 30 days – higher than 28% 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 29 Aug 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-41351, organizations should implement strict input validation and output encoding on all user-supplied data processed by the vulnerable getContent.php script and related components. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of potential XSS attacks. Disable or restrict the use of UMEditor or similar vulnerable components if they are not essential, or isolate them behind authentication and network controls to limit exposure. Monitor web application logs for suspicious activity indicative of XSS attempts. Educate users about the risks of clicking on untrusted links or interacting with suspicious content. Additionally, consider deploying Web Application Firewalls (WAFs) with rules designed to detect and block XSS payloads targeting the affected endpoint. Regular security assessments and code reviews focusing on input handling can prevent similar vulnerabilities in the future.
Description
bjyadmin commit a560fd5 is vulnerable to Cross Site Scripting (XSS) via Public/statics/umeditor1_2_3/php/getContent.php