Fortimanager FirmwareOperating system · Fortinet
CVE-2015-7363
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 · uneditedCross-site scripting (XSS) vulnerability in the advanced settings page in Fortinet FortiManager 5.x before 5.0.12 and 5.2.x before 5.2.3, in hardware models with a hard disk, and FortiAnalyzer 5.x before 5.0.13 and 5.2.x before 5.2.3 allows remote administrators to inject arbitrary web script or HTML via vectors related to report filters.
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 · high confidenceA stored Cross-Site Scripting (XSS) vulnerability exists in the advanced settings page of Fortinet FortiManager (5.x before 5.0.12 and 5.2.x before 5.2.3) and FortiAnalyzer (5.x before 5.0.13 and 5.2.x before 5.2.3) on hardware models with hard drives. Authenticated remote administrators can inject arbitrary JavaScript or HTML through report filter vectors, potentially allowing session hijacking or credential theft when other administrators view the affected settings page.
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
Fortimanager FirmwareOperating system
= 5.0.0= 5.0.1= 5.0.2= 5.0.3= 5.0.4= 5.0.5= 5.0.6= 5.0.7= 5.0.8= 5.0.9= 5.0.10= 5.0.11
Fortianalyzer FirmwareOperating system
= 5.0.0= 5.0.1= 5.0.2= 5.0.3= 5.0.4= 5.0.5= 5.0.6= 5.0.7= 5.0.8= 5.0.9= 5.0.10= 5.0.11CVSS 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.0/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 product and firmware versionRun 'get system status' in CLI or check the dashboard in web UI to determine if the device is FortiManager or FortiAnalyzer and note the firmware versionAffected if The firmware version is 5.0.0 through 5.0.11, or 5.2.0 through 5.2.2 for either product
-
Verify hardware model has hard drivesCheck the hardware model specifications or run 'get hardware info' in CLI to confirm if the model includes internal hard drivesAffected if The device is a hardware model with hard drives (this is required for the vulnerability to be applicable)
-
Confirm administrator access to advanced settingsLog in as an administrator and navigate to the advanced settings page, typically under System > Settings or Reports > Settings in the web UIAffected if The authenticated administrator has access to the advanced settings page containing report filter configuration
-
Inspect report filter entries for malicious contentReview existing report filter configurations by accessing the report filter settings area and examining any stored filter values for unsanitized inputAffected if Any report filter entries contain unsanitized JavaScript or HTML tags (indicated by unexpected script, iframe, img onerror, or similar tags in filter fields)
-
Check for unauthorized session activityReview admin audit logs for any suspicious actions or session anomalies originating from the advanced settings page areaAffected if Audit logs show unexpected actions or sessions initiated from the report filter functionality
You are affected if you are running FortiManager 5.0.0-5.0.11 or 5.2.0-5.2.2, or FortiAnalyzer 5.0.0-5.0.11 or 5.2.0-5.2.2, on a hardware model with hard drives, and the advanced settings page with report filters is accessible to authenticated administrators.
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 dataUpgrade FortiManager to version 5.0.12 or 5.2.3+ and FortiAnalyzer to version 5.0.13 or 5.2.3+ to remediate this vulnerability. Alternatively, implement strict input validation and output encoding on the report filter functionality as a compensating control until patching is feasible.
Fix this in Fortimanager Firmware
Scoped from the published advisory
- Consultation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7363 — 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-2015-7363 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