dbcve.org
FortimanagerApplication · Fortinet

CVE-2022-26121

MEDIUM · 5.3 CVSS v3.1 Published 2022-10-10
Fix available
A fix is available. Upgrade to after 7.0.3 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 exposure of resource to wrong sphere vulnerability [CWE-668] in FortiAnalyzer and FortiManager GUI 7.0.0 through 7.0.3, 6.4.0 through 6.4.8, 6.2.0 through 6.2.9, 6.0.0 through 6.0.11, 5.6.0 through 5.6.11 may allow an unauthenticated and remote attacker to access report template images via referencing the name in the URL path.

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

An unauthenticated remote attacker can access report template images on FortiAnalyzer and FortiManager GUI interfaces (versions 7.0.0-7.0.3, 6.4.0-6.4.8, 6.2.0-6.2.9, 6.0.0-6.0.11, 5.6.0-5.6.11) by directly referencing image names in the URL path, due to improper access control allowing exposure of resources to unauthenticated users (CWE-668).

MitigationUpgrade to FortiAnalyzer/FortiManager version 7.0.4, 6.4.9, 6.3.0, 6.0.12, or 5.6.12 or later. As an interim control, restrict network access to the GUI management interface to trusted IP addresses via firewall rules or SSL VPN.

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
FortimanagerApplication
Affected:> 5.6.0, <= 5.6.11> 6.0.0, <= 6.0.11> 6.2.0, <= 6.2.9> 6.4.0, <= 6.4.8> 7.0.0, <= 7.0.3
FortianalyzerApplication
Affected:> 5.6.0, <= 5.6.11> 6.0.0, <= 6.0.11> 6.2.0, <= 6.2.9> 6.4.0, <= 6.4.8> 7.0.0, <= 7.0.3

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 installed FortiManager or FortiAnalyzer version
    Run 'get system status' or 'diag -d sys version' via CLI, or check the GUI login page footer for version number
    Affected if Version falls within 5.6.0-5.6.11, 6.0.0-6.0.11, 6.2.0-6.2.9, 6.4.0-6.4.8, or 7.0.0-7.0.3
  2. Confirm GUI interface is enabled and accessible
    Check system settings via CLI with 'get system interface' or 'show system interface' to verify the management GUI port (typically 443 or 4433) is bound to an accessible interface
    Affected if GUI is enabled on an interface reachable from untrusted networks
  3. Test unauthenticated access to report template images
    Attempt to access a report template image URL directly without authentication, such as: GET /static/report_template_images/[imagename].png or similar paths under /static/ or /report/ - check if HTTP 200 is returned instead of redirect to login
    Affected if HTTP 200 response with image content is returned without requiring authentication

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.3
Interim mitigation

Upgrade to FortiAnalyzer/FortiManager version 7.0.4, 6.4.9, 6.3.0, 6.0.12, or 5.6.12 or later. As an interim control, restrict network access to the GUI management interface to trusted IP addresses via firewall rules or SSL VPN.

Recommended fix Moderate confidence

Upgrade to the latest available FortiManager/FortiAnalyzer release in your current major version branch (minimum: 7.0.4, 6.4.9, 6.2.10, 6.0.12, or 5.6.12)

  1. 1. Identify the current FortiManager and FortiAnalyzer versions running in your environment
  2. 2. For FortiManager: Determine which version branch is in use (5.6.x, 6.0.x, 6.2.x, 6.4.x, or 7.0.x)
  3. 3. For FortiAnalyzer: Determine which version branch is in use (5.6.x, 6.0.x, 6.2.x, 6.4.x, or 7.0.x)
  4. 4. For FortiManager 7.0.x: Upgrade to version 7.0.4 or later
  5. 5. For FortiManager 6.4.x: Upgrade to version 6.4.9 or later
  6. 6. For FortiManager 6.2.x: Upgrade to version 6.2.10 or later
  7. 7. For FortiManager 6.0.x: Upgrade to version 6.0.12 or later
  8. 8. For FortiManager 5.6.x: Upgrade to version 5.6.12 or later
Caveat Minor: Review Fortinet release notes for any configuration changes or deprecated features between your current version and the target version

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

Fix this in Fortimanager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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