dbcve.org
FortianalyzerApplication · Fortinet

CVE-2021-24021

MEDIUM · 5.4 CVSS v3.1 Published 2021-10-06
Fix available
A fix is available. Upgrade to 6.2.8 / 6.4.4 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
An improper neutralization of input vulnerability [CWE-79] in FortiAnalyzer versions 6.4.3 and below, 6.2.7 and below and 6.0.10 and below may allow a remote authenticated attacker to perform a stored cross site scripting attack (XSS) via the column settings of Logview in FortiAnalyzer, should the attacker be able to obtain that POST request, via other, hypothetical attacks.

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 confidence

A stored cross-site scripting (XSS) vulnerability in FortiAnalyzer's Logview column settings allows remote authenticated attackers to inject malicious script via unsanitized POST parameters in column configuration. The injected payload persists and executes when other users view the Logview interface.

MitigationApply vendor patches: upgrade to FortiAnalyzer 6.4.4+, 6.2.8+, or 6.0.11+ to resolve the input validation failure in Logview column settings.

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
FortianalyzerApplication
Affected:>= 6.0.0, < 6.2.8>= 6.4.0, < 6.4.4

CVSS 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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify FortiAnalyzer installation
    Locate FortiAnalyzer in your environment and confirm it is the affected product. Check network inventory or consult your system documentation for deployment details.
    Affected if FortiAnalyzer is deployed in the environment
  2. Check installed FortiAnalyzer version
    Access the FortiAnalyzer web UI (System > Settings > Dashboard) or use CLI command 'get system status' to retrieve the firmware version number.
    Affected if Version is 6.0.0 through 6.0.10, 6.2.0 through 6.2.7, or 6.4.0 through 6.4.3 (falls within < 6.2.8 or < 6.4.4)
  3. Confirm Logview feature accessibility
    Verify that the Logview interface is accessible to users. Log in with an authenticated account and navigate to Log View or Log View > Log Browse to confirm the feature is enabled and usable.
    Affected if Logview is accessible and users can interact with column settings
  4. Inspect column configuration storage
    Review the column configuration data stored in FortiAnalyzer. In the web UI, go to Log View > Column Settings, or use CLI command 'log-viewer column-config get' if available, to examine configured columns.
    Affected if Any column names or settings contain unexpected characters or appear to be encoded script tags (such as <script> or javascript:)

If FortiAnalyzer is deployed with a version in the affected ranges and the Logview feature is accessible, the environment may be vulnerable to stored XSS through column configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 6.2.8 / 6.4.4 or later
Fixed in 6.2.86.4.4
Interim mitigation

Apply vendor patches: upgrade to FortiAnalyzer 6.4.4+, 6.2.8+, or 6.0.11+ to resolve the input validation failure in Logview column settings.

Recommended fix High confidence

FortiAnalyzer 6.2.8 or later for 6.2.x branch; FortiAnalyzer 6.4.4 or later for 6.4.x branch

  1. 1. Identify the currently installed FortiAnalyzer version using the Web UI (System Settings > Dashboard > Status) or CLI: 'get system status'
  2. 2. For FortiAnalyzer 6.0.x versions: Upgrade to version 6.2.8 or later (preferably 6.4.4 or later for longer support)
  3. 3. For FortiAnalyzer 6.2.x versions below 6.2.8: Upgrade to version 6.2.8 or later
  4. 4. For FortiAnalyzer 6.4.0-6.4.3: Upgrade to version 6.4.4 or later
  5. 5. Download the firmware from Fortinet's support portal (https://support.fortinet.com/)
  6. 6. Backup the FortiAnalyzer configuration before upgrading
  7. 7. Upload and install the firmware via Web UI (System Settings > Firmware) or CLI: 'execute restore config <filename>' after uploading via FTP/TFTP
  8. 8. After upgrade, verify the version and ensure all services are operational
Caveat Review FortiAnalyzer release notes for migration considerations; some older report templates or custom configurations may require adjustment after major version upgrades

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortianalyzer Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-24021 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-24021 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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