dbcve.org
FortianalyzerApplication · Fortinet

CVE-2022-39950

MEDIUM · 5.4 CVSS v3.1 Published 2022-11-02
Fix available
A fix is available. Upgrade to after 7.0.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 during web page generation vulnerability [CWE-79] exists in FortiManager and FortiAnalyzer 6.0.0 all versions, 6.2.0 all versions, 6.4.0 through 6.4.8, and 7.0.0 through 7.0.4. Report templates may allow a low privilege level attacker to perform an XSS attack via posting a crafted CKeditor "protected" comment as described in CVE-2020-9281.

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 confidence

This is a stored Cross-Site Scripting (XSS) vulnerability (CWE-79) in FortiManager and FortiAnalyzer web interfaces. A low-privilege attacker can inject malicious JavaScript code via crafted CKeditor 'protected' comments embedded in report templates. The vulnerability is a regression or related issue to CVE-2020-9281 which had similar CKeditor protected comment injection.

MitigationUpgrade to FortiManager and FortiAnalyzer versions 7.0.5 or later, or 7.2.0 or later where the vulnerability is patched. As a temporary measure, disable or restrict report template creation/modification for low-privilege users.

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.9>= 6.4.0, <= 6.4.8>= 7.0.0, <= 7.0.4
FortimanagerApplication
Affected:>= 6.0.0, <= 6.2.9>= 6.4.0, <= 6.4.8>= 7.0.0, <= 7.0.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
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 checks

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

  1. Determine FortiAnalyzer version
    Log into the FortiAnalyzer web interface and check the version displayed on the login page footer, or use the CLI command 'get system status' to retrieve the firmware version.
    Affected if The installed version falls within 6.0.0 to 6.2.9, 6.4.0 to 6.4.8, or 7.0.0 to 7.0.4.
  2. Determine FortiManager version
    Log into the FortiManager web interface and check the version displayed on the login page footer, or use the CLI command 'get system status' to retrieve the firmware version.
    Affected if The installed version falls within 6.0.0 to 6.2.9, 6.4.0 to 6.4.8, or 7.0.0 to 7.0.4.
  3. Verify access to report template functionality
    Navigate to the Reports section in the web UI and confirm whether report templates can be created, edited, or modified. Check user account permissions to determine if low-privilege users have access to this feature.
    Affected if The report template creation or modification feature is accessible to the user being assessed, particularly low-privilege accounts.
  4. Inspect CKeditor usage in report templates
    In the Reports section, open any existing report templates and examine if the CKeditor rich text editor is used for template editing. Look for the presence of the CKeditor interface when modifying templates.
    Affected if CKeditor is enabled and used for editing report templates in the web interface.

A user is affected if their FortiManager or FortiAnalyzer version is within the listed vulnerable ranges AND the report template feature with CKeditor is accessible to low-privilege users.

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 a release after 7.0.4
Interim mitigation

Upgrade to FortiManager and FortiAnalyzer versions 7.0.5 or later, or 7.2.0 or later where the vulnerability is patched. As a temporary measure, disable or restrict report template creation/modification for low-privilege users.

Recommended fix Moderate confidence

Upgrade to FortiManager/FortiAnalyzer 7.0.5 or later (or 6.4.9+ for 6.4.x branch)

  1. 1. Identify the current FortiManager or FortiAnalyzer version using the Web UI (System Settings > Dashboard > System Information) or CLI: get system status
  2. 2. Based on the current major version, plan upgrade path: For 6.0.x-6.2.x: upgrade to 6.4.9 or later; For 6.4.x: upgrade to 6.4.9 or later (or 7.0.5+); For 7.0.x: upgrade to 7.0.5 or later
  3. 3. Backup the FortiManager/FortiAnalyzer configuration before upgrading
  4. 4. Download the appropriate firmware from Fortinet Customer Support portal (https://support.fortinet.com)
  5. 5. Upload and install the firmware via Web UI (System Settings > Firmware) or CLI: execute restore config <filename>
  6. 6. After upgrade, verify the system is operational and test report templates to confirm the vulnerability is remediated
Caveat Review Fortinet release notes for the target version for any configuration or feature changes that may require adjustment

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

Fix this in Fortianalyzer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-39950 — 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-2022-39950 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