dbcve.org
FortiosOperating system · Fortinet

CVE-2024-26006

MEDIUM · 6.1 CVSS v3.1 Published 2025-03-14
Fix available
A fix is available. Upgrade to 7.0.14 / 7.0.17 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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] in FortiOS version 7.4.3 and below, version 7.2.7 and below, version 7.0.13 and below and FortiProxy version 7.4.3 and below, version 7.2.9 and below, version 7.0.16 and below web SSL VPN UI may allow a remote unauthenticated attacker to perform a Cross-Site Scripting attack via a malicious samba server.

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

Cross-site scripting vulnerability in FortiOS and FortiProxy SSL VPN web interface allows remote unauthenticated attackers to inject malicious scripts via a malicious samba server. The vulnerability stems from improper input validation in the web page generation process (CWE-79).

MitigationUpgrade to FortiOS 7.4.4/7.2.8/7.0.14 or later, and FortiProxy 7.4.4/7.2.10/7.0.17 or later. Until patched, restrict access to SSL VPN and monitor for suspicious samba server connections.

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
FortiosOperating system
Affected:>= 6.4.0, < 7.0.14>= 7.2.0, < 7.2.8>= 7.4.0, < 7.4.4
FortiproxyApplication
Affected:>= 7.0.0, < 7.0.17>= 7.2.0, < 7.2.10>= 7.4.0, < 7.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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify the installed product
    Run 'get system status' or 'diag sys version' via FortiOS/FortiProxy CLI to confirm whether the device runs FortiOS or FortiProxy.
    Affected if The device is running FortiOS or FortiProxy firmware.
  2. Determine the firmware version
    Execute 'get system status' in the CLI and locate the 'FortiOS' or 'FortiProxy' version field, for example: FortiOS v7.2.5.
    Affected if The version is within any of the affected ranges: FortiOS >= 6.4.0 and < 7.0.14, >= 7.2.0 and < 7.2.8, >= 7.4.0 and < 7.4.4; or FortiProxy >= 7.0.0 and < 7.0.17, >= 7.2.0 and < 7.2.10, >= 7.4.0 and < 7.4.4.
  3. Verify SSL VPN web interface is enabled
    Run 'get vpn ssl settings' in the CLI and check if 'status' is enabled or if web-mode is configured.
    Affected if SSL VPN web interface is actively enabled on the device.
  4. Review logs for suspicious samba server connections
    Execute 'execute log filter category 23' followed by 'execute log display' or check GUI logs for connections from unexpected SMB/samba servers to the SSL VPN portal.
    Affected if Logs show connections from unknown or untrusted samba servers to the SSL VPN interface.

The device is affected if it runs FortiOS or FortiProxy within the listed version ranges AND has SSL VPN web interface enabled.

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 7.0.14 / 7.0.17 / 7.2.8 or later
Fixed in 7.0.147.0.177.2.8
Interim mitigation

Upgrade to FortiOS 7.4.4/7.2.8/7.0.14 or later, and FortiProxy 7.4.4/7.2.10/7.0.17 or later. Until patched, restrict access to SSL VPN and monitor for suspicious samba server connections.

Recommended fix High confidence

FortiOS: 7.4.4+ / 7.2.8+ / 7.0.14+ | FortiProxy: 7.4.4+ / 7.2.10+ / 7.0.17+

  1. 1. Identify the currently installed FortiOS or FortiProxy version using the web UI or CLI command 'get system status'
  2. 2. Determine which version branch you are running (7.0.x, 7.2.x, or 7.4.x)
  3. 3. For FortiOS 7.4.x users: Upgrade to FortiOS 7.4.4 or later
  4. 4. For FortiOS 7.2.x users: Upgrade to FortiOS 7.2.8 or later
  5. 5. For FortiOS 7.0.x users: Upgrade to FortiOS 7.0.14 or later
  6. 6. For FortiProxy 7.4.x users: Upgrade to FortiProxy 7.4.4 or later
  7. 7. For FortiProxy 7.2.x users: Upgrade to FortiProxy 7.2.10 or later
  8. 8. For FortiProxy 7.0.x users: Upgrade to FortiProxy 7.0.17 or later
Caveat Standard upgrade risks apply - review release notes for compatibility notes and backup configuration before upgrading

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

Fix this in Fortios Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
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,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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