FortisiemApplication · Fortinet
CVE-2019-17651
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 · uneditedAn Improper Neutralization of Input vulnerability in the description and title parameters of a Device Maintenance Schedule in FortiSIEM version 5.2.5 and below may allow a remote authenticated attacker to perform a Stored Cross Site Scripting attack (XSS) by injecting malicious JavaScript code into the description field of a Device Maintenance schedule.
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 confidenceA stored XSS vulnerability exists in FortiSIEM's Device Maintenance Schedule feature where the description and title parameters do not properly sanitize user input, allowing an authenticated attacker to inject malicious JavaScript code that executes when other users view the maintenance schedule.
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
<= 5.2.5CVSS 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 versionAccess the FortiSIEM GUI (or via CLI command 'phxadmin version'), navigate to System > Settings > About, or check the login page footer for version number. Compare against the affected range: version 5.2.5 or lower.Affected if The installed version is FortiSIEM 5.2.5 or any version lower than 5.2.5.
-
Verify Device Maintenance Schedule feature existsLog into FortiSIEM as an authenticated user and navigate to the Device Maintenance Schedule (typically under Device > Setup > Maintenance Schedule or a similar path in the GUI). Determine if this feature interface is present and accessible.Affected if The Device Maintenance Schedule feature is present and accessible in the FortiSIEM interface.
-
Check for scheduled maintenance entriesIn the Device Maintenance Schedule interface, review any existing scheduled maintenance entries. Inspect the Title and Description fields of each entry for suspicious script tags (<script>), event handlers (onerror, onload, etc.), or encoded JavaScript.Affected if Any maintenance schedule entries contain unsanitized HTML or JavaScript in the title or description fields.
-
Confirm authenticated user accessVerify that regular authenticated users (non-admin) can access the Device Maintenance Schedule feature to create or view maintenance entries. Check role-based access controls and permissions.Affected if Authenticated users have permissions to create or view maintenance schedule entries.
A user is affected if FortiSIEM version is 5.2.5 or lower, the Device Maintenance Schedule feature is accessible, and malicious scripts can be injected into the title or description fields to execute when other users view the schedule.
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 for FortiSIEM. Until then, implement input validation and output encoding on the description and title fields, and consider disabling the Device Maintenance Schedule feature if not required.
Fix this in Fortisiem
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17651 — 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-2019-17651 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