dbcve.org
FortiwebApplication · Fortinet

CVE-2025-25254

HIGH · 7.2 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 7.4.7 / 7.6.3 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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability [CWE-22] in FortiWeb version 7.6.2 and below, version 7.4.6 and below, 7.2 all versions, 7.0 all versions endpoint may allow an authenticated admin to access and modify the filesystem 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 · high confidence

FortiWeb web application firewall contains a path traversal vulnerability (CWE-22) allowing authenticated administrators to escape restricted directories and access or modify the filesystem using specially crafted requests. The vulnerability affects multiple version branches including 7.0, 7.2, 7.4 (up to 7.4.6), and 7.6 (up to 7.6.2).

MitigationApply the vendor patch for FortiWeb; version 7.4.7 addresses the vulnerability in the 7.4 branch, and version 7.6.3 addresses it in the 7.6 branch. Upgrade to a fixed version and restrict admin access to trusted personnel only.

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.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 installation and version
    Log into the FortiWeb CLI and run the command: `get system status` or check the web UI Dashboard > System Information widget to view the firmware version
    Affected if The displayed version falls within the ranges >= 7.0.0 and < 7.4.7, or >= 7.6.0 and < 7.6.3
  2. Confirm admin access is enabled
    In the web UI, go to System > Admin > Administrators or run `show system admin` in CLI to list admin accounts
    Affected if Any administrator account exists and is accessible, as the vulnerability requires authenticated admin privileges
  3. Check for exposed admin interface
    Review network configuration via System > Network > Interface in the web UI or run `show system interface` in CLI to identify if the admin HTTPS port (port 443) is bound to an external or untrusted interface
    Affected if The admin interface is reachable from untrusted networks (WAN/outside interfaces)
  4. Review logs for path traversal attempts
    In the web UI, go to Log & Report > Event Log and filter for events containing patterns like '../' or '..\' in URI parameters, or run CLI command: `execute log filter category event` and search for suspicious path patterns
    Affected if Logs show unusual path traversal patterns in admin API requests, particularly from admin user sessions

You are affected if FortiWeb version is 7.0.0 through 7.4.6, or 7.6.0 through 7.6.2, and the admin interface is accessible with valid credentials.

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

Apply the vendor patch for FortiWeb; version 7.4.7 addresses the vulnerability in the 7.4 branch, and version 7.6.3 addresses it in the 7.6 branch. Upgrade to a fixed version and restrict admin access to trusted personnel only.

Recommended fix High confidence

FortiWeb 7.4.7 or later, or 7.6.3 or later (depending on which version branch you are on)

  1. 1. Identify the currently installed FortiWeb version via Web UI (System > Status) or CLI: `get system status`
  2. 2. For FortiWeb 7.0.x and 7.2.x: Plan migration path to version 7.4.7 or later, or the latest stable 7.6 line
  3. 3. For FortiWeb 7.4.x: Upgrade to version 7.4.7 or later
  4. 4. For FortiWeb 7.6.x: Upgrade to version 7.6.3 or later
  5. 5. Before upgrading, backup the FortiWeb configuration via Web UI (System > Maintenance > Backup) or CLI: `execute backup config`
  6. 6. Download the firmware from Fortinet Customer Support portal or FortiGuard
  7. 7. Upload and install the new firmware via Web UI (System > Maintenance > Firmware) or CLI: `execute system firmware upgrade`
  8. 8. After reboot, verify the upgrade was successful and confirm the new version: `get system status`
Caveat Review Fortinet release notes for the target version for any configuration or behavioral changes before upgrading; always test in a 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
  • Consultation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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