Open Redirect in Fortinet Fortios (CVE-2025-47890)
Summary
Vulnerability in Fortinet Fortios (CVE-2025-47890). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
An URL Redirection to Untrusted Site vulnerabilities [CWE-601] in FortiOS 7.6.0 through 7.6.2, 7.4.0 through 7.4.8, 7.2 all versions, 7.0 all versions, 6.4 all versions; FortiProxy 7.6.0 through 7.6.3, 7.4 all versions, 7.2 all versions, 7.0 all versions; FortiSASE 25.2.a may allow an unauthenticated attacker to perform an open redirect attack via crafted HTTP requests.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-47890 has been found in Fortinet Fortios.
Risk of unauthorized operations or information disclosure. CVSS score: 2.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Fortinet Fortios CVE-2025-47890" on the vendor's site.
CVE-2025-47890 (Fortinet Fortios) — CWE-601 / CVSS v3 2.6
Attack vector: adjacent-network / unauthenticated
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-601) exists in Fortinet Fortios.
Check the vendor advisory for the affected versions of Fortinet Fortios.
Severity: Low (CVSS 2.6/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Fortios' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Fortios' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Fortiosを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- patch psirt@fortinet.com
- web cert-portal.siemens.com
- web nvd.nist.gov
- web github.com