FortiportalApplication · Fortinet
CVE-2025-24470
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 · uneditedAn Improper Resolution of Path Equivalence vulnerability [CWE-41] in FortiPortal 7.4.0 through 7.4.2, 7.2.0 through 7.2.6, 7.0.0 through 7.0.11 may allow a remote unauthenticated attacker to retrieve source code 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 confidenceFortiPortal versions 7.0.0-7.0.11, 7.2.0-7.2.6, and 7.4.0-7.4.2 contain a path equivalence vulnerability (CWE-41) allowing unauthenticated remote attackers to retrieve source code through crafted HTTP requests. This is a path traversal vulnerability where the application fails to properly resolve path sequences, enabling access to sensitive files outside the web root.
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
FortiportalApplication
>= 7.0.0, < 7.0.12>= 7.2.0, < 7.2.7>= 7.4.0, < 7.4.3CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify FortiPortal versionLog into the FortiPortal admin console and navigate to System Settings > About, or use the CLI command 'get system status' to retrieve the installed version numberAffected if The installed version is 7.0.0 through 7.0.11, 7.2.0 through 7.2.6, or 7.4.0 through 7.4.2
-
Verify network exposureConfirm whether the FortiPortal web interface is accessible from untrusted networks by reviewing firewall rules, NAT configurations, or reverse proxy settings that expose port 443 or 80 externallyAffected if FortiPortal HTTP/HTTPS ports are reachable from the internet or untrusted networks without filtering
-
Inspect HTTP access logs for path traversal attemptsReview FortiPortal or upstream proxy logs for requests containing patterns such as '../', '..\', URL-encoded variations (%2e%2e/), or attempts to access sensitive paths like /etc/passwd, WEB-INF, or configuration filesAffected if Logs show suspicious requests with path traversal sequences targeting files outside the web root
-
Check for unauthorized file access indicatorsExamine web server logs and file system for evidence of access to source code, configuration files, or other sensitive files that should not be publicly accessibleAffected if Logs or file access records indicate retrieval of source code or configuration files via crafted URLs
If FortiPortal version is within 7.0.0-7.0.11, 7.2.0-7.2.6, or 7.4.0-7.4.2 AND the service is network-accessible, the environment is likely affected by this path traversal vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.0.127.2.77.4.3
Apply vendor-supplied patches (FortiPortal 7.4.3, 7.2.7, 7.0.12 or later). As a temporary measure, restrict exposure of FortiPortal to trusted networks or implement WAF rules to block path traversal patterns in HTTP requests.
FortiPortal 7.4.3 (or latest 7.x release)
- Identify the currently installed FortiPortal version using the management interface or CLI
- Determine which version branch is in use (7.0.x, 7.2.x, or 7.4.x)
- If on 7.0.x branch: upgrade to FortiPortal 7.0.12 or later
- If on 7.2.x branch: upgrade to FortiPortal 7.2.7 or later
- If on 7.4.x branch: upgrade to FortiPortal 7.4.3 or later
- Before upgrading, backup the current configuration and data
- Perform the upgrade during a planned maintenance window
- After upgrade, verify the version and test that the application functions normally
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortiportal
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24470 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24470 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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