FortisiemApplication · Fortinet
CVE-2024-27780
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerabilities [CWE-79] in FortiSIEM 7.1 all versions, 7.0 all versions, 6.7 all versions incident page may allow an authenticated attacker to perform a cross-site scripting attack via crafted HTTP requests.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceStored XSS vulnerability in FortiSIEM incident page allows authenticated attackers to inject malicious JavaScript via crafted HTTP requests. The input is not properly sanitized before being rendered in the web page, enabling script execution in the context of other users' sessions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FortisiemApplication
>= 6.7.0, <= 6.7.9>= 7.0.0, <= 7.0.3>= 7.1.0, <= 7.1.8CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify FortiSIEM versionRun the command 'fortisiem-cli get version' or check the FortiSIEM dashboard under Admin > System Settings > General to find the installed version numberAffected if The installed version falls within 6.7.0-6.7.9, 7.0.0-7.0.3, or 7.1.0-7.1.8
-
Verify incident page accessLog into FortiSIEM as an authenticated user and navigate to the Incidents page (Incidents > Dashboard) to confirm the web interface is accessibleAffected if The incident management web interface is available and operational
-
Inspect audit logs for XSS patternsCheck FortiSIEM audit logs under Admin > Audit Logs for any incident entries containing script tags, javascript:, or other XSS payloads in incident title, description, or comment fieldsAffected if Audit logs show incident entries containing suspicious script injection patterns that were not sanitized
-
Review web server logs for exploitation attemptsExamine FortiSIEM web server logs (typically in /opt/phoenix/log or equivalent) for POST requests to incident creation or update endpoints containing XSS payloadsAffected if Web logs show requests with XSS payloads targeting the incident page that were successfully stored
A user is affected if FortiSIEM is running any version between 6.7.0-6.7.9, 7.0.0-7.0.3, or 7.1.0-7.1.8 and the incident management web interface is accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-supplied patch from Fortinet for FortiSIEM 6.7, 7.0, and 7.1 versions. As an interim control, implement strict input validation and output encoding on the incident page, and consider restricting access to the incident page to trusted users only.
Fix this in Fortisiem
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27780 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-27780 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data