dbcve.org
FortiwebApplication · Fortinet

CVE-2024-46671

HIGH · 7.2 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 7.2.11 / 7.4.7 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 Incorrect User Management vulnerability [CWE-286] in FortiWeb version 7.6.2 and below, version 7.4.6 and below, version 7.2.10 and below, version 7.0.11 and below widgets dashboard may allow an authenticated attacker with at least read-only admin permission to perform operations on the dashboard of other administrators via crafted 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

FortiWeb widget dashboard has an incorrect user management vulnerability where an authenticated attacker with read-only admin permission can perform operations on other administrators' dashboards via crafted HTTP requests, representing a horizontal privilege escalation (CWE-286).

MitigationApply FortiWeb vendor patches for versions 7.6.2, 7.4.6, 7.2.10, and 7.0.11 and below to remediate the authorization bypass in the widget dashboard component.

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
FortiwebApplication
Affected:>= 7.0.0, < 7.2.11>= 7.4.0, < 7.4.7>= 7.6.0, < 7.6.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
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 FortiWeb version
    Run the command: get system status or execute 'fortiweb -v' via CLI, or check the FortiWeb web UI under System > Status to view the firmware version
    Affected if The installed version falls within 7.0.0 through 7.0.x (below 7.0.11), 7.2.0 through 7.2.x (below 7.2.10), 7.4.0 through 7.4.x (below 7.4.6), or 7.6.0 through 7.6.x (below 7.6.2)
  2. Confirm widget dashboard is in use
    Log into FortiWeb web UI and navigate to the dashboard view. Check if any custom widgets are configured or if multiple dashboard configurations exist under Dashboard > Dashboard > All Dashboards
    Affected if Widget dashboard functionality is actively used or configured with multiple administrator dashboards
  3. Review administrator accounts for unauthorized changes
    Go to System > Admin > Administrators and compare the current list of administrators against known legitimate accounts. Look for unexpected modifications to read-only admin accounts or dashboard widget configurations
    Affected if Unauthorized changes exist in administrator configurations or dashboard widget settings that were not performed by the legitimate account owner
  4. Examine audit logs for horizontal privilege escalation
    Go to Log & Report > Event Log > System and filter for events involving widget dashboard operations. Look for API calls or HTTP requests from read-only admin accounts performing write operations on other administrators' dashboards
    Affected if Logs show read-only admin accounts performing operations on dashboards belonging to other administrators, indicating exploitation of the authorization bypass

A user is affected if FortiWeb version is 7.0.0-7.0.10, 7.2.0-7.2.10, 7.4.0-7.4.6, or 7.6.0-7.6.2 AND the widget dashboard feature is in use, with evidence of unauthorized cross-admin dashboard modifications in logs or configuration.

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.11 / 7.4.7 / 7.6.3 or later
Fixed in 7.2.117.4.77.6.3
Interim mitigation

Apply FortiWeb vendor patches for versions 7.6.2, 7.4.6, 7.2.10, and 7.0.11 and below to remediate the authorization bypass in the widget dashboard component.

Recommended fix High confidence

Upgrade to the latest version in your current branch: 7.0.12+, 7.2.11+, 7.4.7+, or 7.6.3+

  1. 1. Identify the current FortiWeb version by navigating to System > Status in the FortiWeb GUI or running 'get system status' in the CLI
  2. 2. Determine which version branch (7.0.x, 7.2.x, 7.4.x, or 7.6.x) your current installation is running
  3. 3. For FortiWeb 7.0.x: Upgrade to version 7.0.12 or later
  4. 4. For FortiWeb 7.2.x: Upgrade to version 7.2.11 or later
  5. 5. For FortiWeb 7.4.x: Upgrade to version 7.4.7 or later
  6. 6. For FortiWeb 7.6.x: Upgrade to version 7.6.3 or later
  7. 7. Download the firmware upgrade from Fortinet's support portal at support.fortinet.com
  8. 8. Upload the firmware via System > Firmware in the GUI or using 'execute firmware upgrade' CLI command
Caveat Standard FortiWeb upgrade considerations apply - review release notes for any configuration or compatibility changes; test in non-production environment first

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

Fix this in Fortiweb Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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