dbcve.org
Forticlient Enterprise Management ServerApplication · Fortinet

CVE-2023-45581

HIGH · 7.2 CVSS v3.1 Published 2024-02-15
Fix available
A fix is available. Upgrade to 7.0.10 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 improper privilege management vulnerability [CWE-269] in Fortinet FortiClientEMS version 7.2.0 through 7.2.2 and before 7.0.10 allows an Site administrator with Super Admin privileges to perform global administrative operations affecting other sites via crafted HTTP or HTTPS 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 · high confidence

A privilege management vulnerability in Fortinet FortiClientEMS versions 7.2.0-7.2.2 and before 7.0.10 allows a site-level administrator with Super Admin privileges to perform unauthorized global administrative operations affecting other sites through crafted HTTP/HTTPS requests. This represents a privilege escalation issue where site-bound administrators can bypass scope boundaries.

MitigationUpgrade FortiClientEMS to version 7.2.3 or later, or version 7.0.10 or later to resolve the improper privilege management.

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
Forticlient Enterprise Management ServerApplication
Affected:< 7.0.10>= 7.2.0, <= 7.2.2

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

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

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 installation and version
    Access the FortiClientEMS management console or use system inventory tools to locate the FortiClientEMS installation and note its exact version number (for example, 7.2.0, 7.2.2, 7.0.9, etc.).
    Affected if The installed version is 7.2.0 through 7.2.2 inclusive, or any version before 7.0.10.
  2. Verify EMS admin account configuration
    In the FortiClientEMS console, navigate to Administration > Administrators to review the list of configured administrators. Identify whether any administrators are assigned to a specific site (rather than being Global admins).
    Affected if There exists a site-level administrator account that has been granted Super Admin privileges.
  3. Review administrator scope assignments
    In the FortiClientEMS console under Administration > Administrators, examine the scope column for each administrator account to determine which are scoped to individual sites versus having global scope.
    Affected if Any Super Admin accounts are assigned to a site-specific scope rather than Global scope.
  4. Audit HTTP/HTTPS request logs for cross-site operations
    In FortiClientEMS, check the Event Log or SQL Server logs for any HTTP/HTTPS requests originating from site-level admin accounts that performed operations on other sites (for example, modifications to endpoints, policies, or configurations outside their assigned site).
    Affected if There are log entries showing site-level administrators executing operations on sites other than their assigned site.

You are affected if FortiClientEMS is running version 7.2.0-7.2.2 or any version below 7.0.10 AND there exist site-level administrators with Super Admin privileges that could potentially perform cross-site operations.

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.10 or later
Fixed in 7.0.10
Interim mitigation

Upgrade FortiClientEMS to version 7.2.3 or later, or version 7.0.10 or later to resolve the improper privilege management.

Recommended fix High confidence

FortiClient EMS 7.0.10 or later, or 7.2.3 or later

  1. 1. Backup the FortiClient EMS configuration and database before upgrading
  2. 2. Download the fixed version (7.0.10 or later for 7.0.x branch, or 7.2.3 or later for 7.2.x branch) from the Fortinet Support Portal
  3. 3. Log in to the FortiClient EMS server with administrative privileges
  4. 4. Navigate to the EMS administration interface and initiate the upgrade process
  5. 5. Upload the downloaded installer and follow the on-screen upgrade wizard
  6. 6. Verify the upgrade was successful by checking the EMS version in the administration console
  7. 7. Test that the privilege management fix is working correctly by verifying site isolation for site administrators

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

Fix this in Forticlient Enterprise Management Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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