dbcve.org
FortiosOperating system · Fortinet

CVE-2025-47890

MEDIUM · 6.1 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 7.4.9 / 7.6.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 URL Redirection to Untrusted Site vulnerabilities [CWE-601] vulnerability in Fortinet FortiOS 7.6.0 through 7.6.3, FortiOS 7.4.0 through 7.4.8, FortiOS 7.2 all versions, FortiOS 7.0 all versions, FortiOS 6.4 all versions, FortiProxy 7.6.0 through 7.6.3, FortiProxy 7.4 all versions, FortiProxy 7.2 all versions, FortiProxy 7.0 all versions, FortiSASE 25.2.a may allow an unauthenticated attacker to perform an open redirect attack via crafted HTTP 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

An unauthenticated open redirect vulnerability (CWE-601) in FortiOS, FortiProxy, and FortiSASE allows attackers to craft malicious HTTP requests that redirect users to arbitrary external sites. The vulnerability affects multiple version ranges across the product lines.

MitigationApply the vendor-supplied patch or upgrade to a FortiOS/FortiProxy version beyond the affected ranges. For FortiSASE, update to the patched release per Fortinet's advisory.

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
FortiosOperating system
Affected:>= 6.4.0, < 7.4.9>= 7.6.0, < 7.6.4
FortiproxyApplication
Affected:>= 7.0.0, < 7.6.4
FortisaseApplication
Affected:= 25.3.40

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 Fortinet product type
    Access the device CLI and run 'get system status' or check the web UI login page footer to confirm whether the device runs FortiOS, FortiProxy, or FortiSASE
    Affected if The device is not one of these three products, then this CVE does not apply
  2. Retrieve the installed FortiOS version
    In CLI, run 'get system status' and note the 'FortiOS' version number shown in the output
    Affected if The version falls within >= 6.4.0 and < 7.4.9, OR within >= 7.6.0 and < 7.6.4, then the system is affected
  3. Retrieve the installed FortiProxy version
    In CLI, run 'get system status' and note the 'FortiProxy' version number shown in the output
    Affected if The version falls within >= 7.0.0 and < 7.6.4, then the system is affected
  4. Retrieve the installed FortiSASE version
    In CLI, run 'get system status' or check the SASE admin portal to identify the exact version number
    Affected if The version is exactly 25.3.40, then the system is affected
  5. Verify web interface exposure
    Determine if the Fortinet web UI or SSL-VPN portal is accessible from untrusted networks by reviewing firewall policies and interface configurations
    Affected if The web interface is externally accessible without authentication, the open redirect can be exploited by remote attackers

You are affected if your device runs FortiOS in version 6.4.0 through 7.4.8 or 7.6.0 through 7.6.3, FortiProxy 7.0.0 through 7.6.3, or FortiSASE exactly version 25.3.40, and the web interface is network-accessible to untrusted users.

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.9 / 7.6.4 or later
Fixed in 7.4.97.6.4
Interim mitigation

Apply the vendor-supplied patch or upgrade to a FortiOS/FortiProxy version beyond the affected ranges. For FortiSASE, update to the patched release per Fortinet's advisory.

Recommended fix High confidence

FortiOS 7.4.9 or later; FortiOS 7.6.4 or later; FortiProxy 7.6.4 or later; FortiSASE 25.3.41 or later

  1. Identify the current FortiOS, FortiProxy, or FortiSASE version running on the device using 'get system status' or the web UI
  2. Download the appropriate firmware upgrade from Fortinet's support portal (fortinet.com/support)
  3. Upload the firmware image to the Fortinet device via web UI (System > Firmware) or CLI: 'execute firmware upgrade <image_name>','Verify the upgrade was successful by checking the new version with 'get system status'
  4. For FortiSASE, upgrade to version 25.3.41 or later as indicated in FortiSASE release notes
Caveat Review Fortinet release notes for potential configuration or feature changes between versions before upgrading; ensure backups of current configuration exist

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

Fix this in Fortios Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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