dbcve.org
FortiswitchOperating system · Fortinet

CVE-2024-48887

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 6.4.15 / 7.0.11 or later.
See remediation →
100/100
Remediation priority · Urgent
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 unverified password change vulnerability in Fortinet FortiSwitch GUI may allow a remote unauthenticated attacker to change admin passwords via a specially crafted request

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

Unverified password change vulnerability in FortiSwitch GUI allows remote unauthenticated attackers to change admin passwords via specially crafted HTTP requests. This authentication bypass in the web interface enables complete administrative account takeover without valid credentials.

MitigationApply the vendor-supplied security patch/firmware update for FortiSwitch. Until patched, restrict GUI access to trusted networks or disable the GUI interface if not required.

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
FortiswitchOperating system
Affected:>= 6.4.0, < 6.4.15>= 7.0.0, < 7.0.11>= 7.2.0, < 7.2.9>= 7.4.0, < 7.4.5= 7.6.0

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm FortiSwitch deployment
    Identify FortiSwitch devices in your environment by checking inventory systems, network documentation, or by querying device hostnames/models via SNMP or network scanning tools.
    Affected if FortiSwitch devices are present in the environment
  2. Check installed firmware version
    Access the FortiSwitch CLI and run the command 'get system status' or use the GUI under System > Firmware to retrieve the current firmware version number.
    Affected if The installed version falls within any of these ranges: 6.4.0 through 6.4.14, 7.0.0 through 7.0.10, 7.2.0 through 7.2.8, 7.4.0 through 7.4.4, or exactly version 7.6.0
  3. Verify GUI interface status
    In FortiSwitch CLI, run 'get system interface' or check via GUI under Network > Interfaces to confirm whether the management GUI interface is enabled and accessible.
    Affected if The HTTP/HTTPS GUI interface is enabled on any interface
  4. Check GUI network accessibility
    Review firewall rules, interface access policies, and ACLs to determine if the FortiSwitch GUI port (HTTP port 80 or HTTPS port 443) is reachable from untrusted or external networks.
    Affected if The GUI is accessible from networks outside your trusted internal network

A user is affected if they have a FortiSwitch running an affected firmware version (6.4.0-6.4.14, 7.0.0-7.0.10, 7.2.0-7.2.8, 7.4.0-7.4.4, or 7.6.0) with the GUI interface enabled and exposed to untrusted networks.

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 6.4.15 / 7.0.11 / 7.2.9 or later
Fixed in 6.4.157.0.117.2.9
Interim mitigation

Apply the vendor-supplied security patch/firmware update for FortiSwitch. Until patched, restrict GUI access to trusted networks or disable the GUI interface if not required.

Recommended fix High confidence

FortiSwitch 6.4.15 / 7.0.11 / 7.2.9 / 7.4.5 (or later stable release in each branch)

  1. 1. Obtain the appropriate fixed firmware version from Fortinet Support portal (https://support.fortinet.com): FortiSwitch 6.4.15, 7.0.11, 7.2.9, or 7.4.5 and above
  2. 2. Verify firmware integrity using checksums provided on the support portal
  3. 3. Back up current FortiSwitch configuration
  4. 4. Access FortiSwitch GUI or use CLI to upload and install the new firmware
  5. 5. After upgrade, verify the device boots correctly and all services are operational
  6. 6. Confirm the admin password has not been altered and monitor for unauthorized access attempts
  7. 7. Review system logs for any indicators of exploitation attempts prior to patching
Caveat Standard firmware upgrade risks apply - ensure configuration backup and plan for brief downtime; test in staging if possible

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

Fix this in Fortiswitch Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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