CVE-2024-28417: Basic XSS
Source CVE Database V5
Not known to be exploited · CVSS 6.3 Medium.
Data as of 26 Oct 2026, 09:15 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:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 14 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
Since no official patches are currently available, organizations should implement immediate mitigations including: 1) Applying strict input validation and output encoding on all user-supplied data, especially on the /webEdition/we_cmd.php endpoint. 2) Employing a Web Application Firewall (WAF) with rules to detect and block common XSS attack patterns targeting this CMS. 3) Restricting access to the vulnerable endpoint to trusted users or internal networks where possible. 4) Conducting thorough security reviews of CMS content inputs and removing any suspicious or untrusted content. 5) Educating users to avoid clicking on suspicious links or interacting with untrusted content served by the CMS. 6) Monitoring logs for unusual activity or attempts to exploit XSS vectors. 7) Planning for an upgrade or patch deployment as soon as a vendor fix becomes available. These steps help reduce the risk until an official patch is released.
Description
Webedition CMS 9.2.2.0 has a Stored XSS vulnerability via /webEdition/we_cmd.php.