CVE-2024-0314: FireEye Central Management · Cross-site Scripting
Affects FireEye Central ManagementSource CVE Database V5
Not known to be exploited · CVSS 5.4 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% 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:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Jan 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-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| FireEye FireEye Central Management | Affected
| Fixed in– |
AI-suggested
Organizations should immediately assess their deployment of FireEye Central Management to identify if version 9.1.1.956704 is in use. In the absence of an official patch, temporary mitigations include: 1) Implementing strict Content Security Policy (CSP) headers to restrict script execution and mitigate XSS impact. 2) Employing web application firewalls (WAFs) with custom rules to detect and block suspicious input patterns targeting the vulnerable parameters. 3) Educating administrators on phishing risks and avoiding clicking on untrusted links that could trigger reflected XSS. 4) Restricting access to the FireEye Central Management interface to trusted networks and VPNs to reduce exposure. 5) Monitoring logs for unusual access patterns or signs of session hijacking. Once FireEye releases a patch, organizations should prioritize prompt deployment. Additionally, reviewing and hardening session management controls (e.g., setting secure, HttpOnly cookies) can reduce the impact of session theft.
Description
XSS vulnerability in FireEye Central Management affecting version 9.1.1.956704, which could allow an attacker to modify special HTML elements in the application and cause a reflected XSS, leading to a session hijacking.