dbcve.org
ForticlientemsApplication · Fortinet

CVE-2025-22859

MEDIUM · 5.3 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 7.4.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
A Relative Path Traversal vulnerability [CWE-23] in FortiClientEMS 7.4.0 through 7.4.1 and FortiClientEMS Cloud 7.4.0 through 7.4.1 may allow a remote unauthenticated attacker to perform a limited arbitrary file write on the system via upload requests.

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

A Relative Path Traversal vulnerability (CWE-23) in FortiClientEMS 7.4.0-7.4.1 and FortiClientEMS Cloud 7.4.0-7.4.1 allows remote unauthenticated attackers to perform limited arbitrary file writes via upload request manipulation.

MitigationUpgrade to FortiClientEMS 7.4.2 or later. As interim measures, restrict network access to the EMS management interface and disable unauthenticated upload endpoints if possible.

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
ForticlientemsApplication
Affected:>= 7.4.0, < 7.4.3
Forticlientems CloudApplication
Affected:>= 7.4.0, < 7.4.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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 FortiClientEMS version
    Log into the EMS management console and navigate to System > Settings > About, or run 'forticlientemsd --version' on the server if CLI access is available
    Affected if The installed version is 7.4.0, 7.4.1, or 7.4.2 (pre-patch) and falls within >= 7.4.0, < 7.4.3
  2. Confirm EMS deployment type
    Determine whether the deployment is FortiClientEMS (on-premises) or FortiClientEMS Cloud by checking the product name in the management console or license information
    Affected if The deployment is either FortiClientEMS or FortiClientEMS Cloud version 7.4.0-7.4.1
  3. Verify network exposure of EMS management interface
    Review firewall rules and access policies to determine if TCP port 443 (HTTPS management) or the configured EMS port is accessible from untrusted networks or the internet
    Affected if The EMS management interface is exposed to unauthenticated or untrusted network segments without restrictive access controls
  4. Check unauthenticated upload endpoint accessibility
    Inspect the EMS configuration or attempt a test request to the upload endpoint (typically /api/v1/upload or similar) from an unauthenticated source to verify if the endpoint accepts requests without authentication
    Affected if The upload endpoints are reachable without authentication and accept request manipulation

You are affected if FortiClientEMS or FortiClientEMS Cloud version is 7.4.0 through 7.4.2 and the management interface or upload endpoints are accessible to unauthenticated 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 7.4.3 or later
Fixed in 7.4.3
Interim mitigation

Upgrade to FortiClientEMS 7.4.2 or later. As interim measures, restrict network access to the EMS management interface and disable unauthenticated upload endpoints if possible.

Recommended fix High confidence

FortiClientEMS 7.4.3 and FortiClientEMS Cloud 7.4.3

  1. Back up the current FortiClientEMS configuration and database
  2. Download FortiClientEMS 7.4.3 from the Fortinet support portal (https://support.fortinet.com)
  3. Review the upgrade guide and release notes for 7.4.3
  4. Upgrade FortiClientEMS to version 7.4.3 following standard Fortinet upgrade procedures
  5. Verify the upgrade was successful and the service is running
  6. Confirm the version by checking the EMS interface or using CLI commands

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

Fix this in Forticlientems Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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