dbcve.org
FortimanagerApplication · Fortinet

CVE-2023-41679

CRITICAL · 9.6 CVSS v3.1 Published 2023-10-10
Fix available
A fix is available. Upgrade to after 7.0.7 or later.
See remediation →
100/100
Remediation priority · Urgent
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 access control vulnerability [CWE-284] in FortiManager management interface 7.2.0 through 7.2.2, 7.0.0 through 7.0.7, 6.4.0 through 6.4.11, 6.2 all versions, 6.0 all versions may allow a remote and authenticated attacker with at least "device management" permission on his profile and belonging to a specific ADOM to add and delete CLI script on other ADOMs

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

FortiManager versions 7.2.0-7.2.2, 7.0.0-7.0.7, 6.4.0-6.4.11, 6.2.x, and 6.0.x contain an improper access control vulnerability (CWE-284) in the management interface. A remote, authenticated attacker with at least 'device management' permission assigned to their profile and belonging to a specific ADOM can add and delete CLI scripts on other ADOMs they should not have access to, bypassing ADOM-level isolation controls.

MitigationApply Fortinet patches for FortiManager: upgrade to 7.2.3 or later, 7.0.8 or later, and 6.4.12 or later. Additionally, audit ADOM permissions and user profiles to ensure least-privilege access is enforced.

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:>= 6.0.0, <= 6.0.12>= 6.2.0, <= 6.2.12>= 6.4.0, <= 6.4.11>= 7.0.0, <= 7.0.7= 7.2.0= 7.2.1= 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
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/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. Check FortiManager version
    Run 'get system status' in FortiManager CLI or check System > Settings > About in the web UI to confirm the installed version
    Affected if Version is 6.0.0-6.0.12, 6.2.0-6.2.12, 6.4.0-6.4.11, 7.0.0-7.0.7, or 7.2.0-7.2.2 (the affected ranges)
  2. Verify ADOM configuration
    In FortiManager web UI, go to System Settings > ADOMs to confirm multiple ADOMs are configured
    Affected if More than one ADOM exists and users are assigned to specific ADOMs (the vulnerability allows bypassing ADOM isolation)
  3. Review user profiles with device management permission
    In FortiManager web UI, go to System Settings > Administrators > Administrator to examine user profiles. Check the 'Device Management' permission field in each profile
    Affected if Any administrator profile has 'Device Management' permission assigned and is limited to a specific ADOM
  4. Audit CLI script ownership across ADOMs
    In FortiManager web UI, go to Policy & Objects > Scripts to list all CLI scripts. Compare the ADOM each script belongs to against which ADOM the creating user is assigned to
    Affected if Scripts exist in ADOMs where the creating user does not have explicit access based on their assigned ADOM
  5. Check for unauthorized script modifications
    Review script execution logs in FortiManager under Log & Report > Event Log > Resource. Look for script add/delete events from users operating outside their assigned ADOM
    Affected if Script add or delete operations appear from users whose profile is restricted to a different ADOM than the target script's ADOM

A user is affected if their FortiManager version falls within the affected ranges AND they have multiple ADOMs configured with users who have device management permissions restricted to specific ADOMs.

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.

From vendor data
Upgrade available Upgrade to a release after 7.0.7
Interim mitigation

Apply Fortinet patches for FortiManager: upgrade to 7.2.3 or later, 7.0.8 or later, and 6.4.12 or later. Additionally, audit ADOM permissions and user profiles to ensure least-privilege access is enforced.

Fix this in Fortimanager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
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,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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