dbcve.org
ForticlientApplication · Fortinet

CVE-2025-31365

HIGH · 7.1 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 7.2.9 / 7.4.4 or later.
See remediation →
78/100
Remediation priority · High
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 Control of Generation of Code ('Code Injection') vulnerability [CWE-94] in FortiClientMac 7.4.0 through 7.4.3, 7.2.1 through 7.2.8 may allow an unauthenticated attacker to execute arbitrary code on the victim's host via tricking the user into visiting a malicious website.

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

Code injection vulnerability (CWE-94) in FortiClientMac versions 7.4.0-7.4.3 and 7.2.1-7.2.8 allows unauthenticated attackers to achieve arbitrary code execution on victims' machines by tricking users into visiting malicious websites, likely through improper handling of code generation or script execution during web requests.

MitigationUpdate FortiClientMac to the latest patched version beyond 7.4.3 and 7.2.8. Until patched, warn users against visiting untrusted websites and consider network-level protections to block known malicious domains.

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
ForticlientApplication
Affected:>= 7.2.1, < 7.2.9>= 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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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. Verify FortiClientMac is installed
    Open Finder, navigate to /Applications folder, and look for FortiClient.app. Alternatively, run: ls /Applications/ | grep -i forti
    Affected if FortiClient.app exists in the Applications folder
  2. Determine installed FortiClient version
    Right-click FortiClient.app, select Get Info, and read the Version number. Or run: defaults read /Applications/FortiClient.app/Contents/Info CFBundleShortVersionString
    Affected if Version returned is 7.2.1 through 7.2.8, or 7.4.0 through 7.4.3
  3. Confirm full version string for precise matching
    Run: defaults read /Applications/FortiClient.app/Contents/Info CFBundleVersion to get the complete version build number if available
    Affected if Version falls within 7.2.1 <= version < 7.2.9 OR 7.4.0 <= version < 7.4.4
  4. Check if FortiClient is currently running
    Open Activity Monitor or run: ps aux | grep -i forti to see if the FortiClient process is active
    Affected if FortiClient is running and version is in the affected range listed above

You are affected if FortiClientMac is installed with a version between 7.2.1 and 7.2.8, or between 7.4.0 and 7.4.3, as the code injection flaw can be triggered when users visit malicious websites.

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.2.9 / 7.4.4 or later
Fixed in 7.2.97.4.4
Interim mitigation

Update FortiClientMac to the latest patched version beyond 7.4.3 and 7.2.8. Until patched, warn users against visiting untrusted websites and consider network-level protections to block known malicious domains.

Recommended fix High confidence

FortiClient 7.2.9 or later, or FortiClient 7.4.4 or later

  1. 1. Check the current FortiClient version by opening FortiClient and navigating to Help > About
  2. 2. Identify which version branch you are currently on (7.2.x or 7.4.x)
  3. 3. For FortiClient 7.2.x users: Navigate to Fortinet's support portal (support.fortinet.com) and download FortiClient version 7.2.9 or later
  4. 4. For FortiClient 7.4.x users: Navigate to Fortinet's support portal and download FortiClient version 7.4.4 or later
  5. 5. Close FortiClient if running
  6. 6. Run the installer for the updated version
  7. 7. Follow the on-screen installation prompts to complete the upgrade
  8. 8. After installation, verify the new version by checking Help > About to confirm the version is 7.2.9+ or 7.4.4+
Caveat Standard upgrade considerations apply - ensure compatibility with your Fortinet gateway/EMS and backup configuration if needed before upgrading

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

Fix this in Forticlient Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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