dbcve.org
FortiadcApplication · Fortinet

CVE-2025-58412

MEDIUM · 6.1 CVSS v3.1 Published 2025-11-19
Fix available
A fix is available. Upgrade to 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
A improper neutralization of script-related html tags in a web page (basic xss) vulnerability in Fortinet FortiADC 8.0.0, FortiADC 7.6.0 through 7.6.3, FortiADC 7.4 all versions, FortiADC 7.2 all versions may allow attacker to execute unauthorized code or commands via crafted URL.

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 · moderate confidence

This is a basic Cross-Site Scripting (XSS) vulnerability in FortiADC's web interface where improper neutralization of script-related HTML tags allows attackers to inject malicious JavaScript via crafted URLs. The vulnerability affects the web management interface and could allow session hijacking or execution of unauthorized commands in the context of authenticated users.

MitigationApply the Fortinet patch for this vulnerability by upgrading to the fixed FortiADC version. Until patches are available, implement URL parameter filtering at the application layer or consider restricting web interface access to trusted networks.

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
FortiadcApplication
Affected:>= 7.2.0, < 7.6.4= 8.0.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
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 the device as FortiADC
    Log into the web UI and check the dashboard or system information page for the device model, or use the CLI command 'get system status' to confirm the device is Fortinet FortiADC
    Affected if The device is not a FortiADC appliance - this CVE only applies to FortiADC
  2. Determine the installed FortiADC version
    In the web UI, navigate to System > Settings or Dashboard > System Information to view the firmware version. Alternatively, use CLI command 'get system status' or 'fnsysctl ls /var/log' to retrieve version details
    Affected if The version is >= 7.2.0 AND < 7.6.4, OR the version equals 8.0.0 exactly
  3. Confirm the web management interface is enabled
    In the web UI, go to System > Administration > Administrators or check the HTTP/HTTPS service status. In CLI, use 'get system interface' to list interfaces with web UI access enabled
    Affected if HTTP or HTTPS management access is enabled on any interface - this is required for the XSS to be exploitable
  4. Assess web interface network exposure
    Review the interface configuration to determine if the web UI is bound to WAN, DMZ, or untrusted networks. Check 'get system interface' output for each interface's IP assignment and access permissions
    Affected if The web management interface is reachable from untrusted or external networks rather than only from isolated management networks

A user is affected if they are running FortiADC versions 7.2.0 through 7.6.3 or version 8.0.0 AND have the web management interface enabled and exposed, even to internal networks, as the XSS can be triggered by authenticated users viewing crafted URLs.

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

Apply the Fortinet patch for this vulnerability by upgrading to the fixed FortiADC version. Until patches are available, implement URL parameter filtering at the application layer or consider restricting web interface access to trusted networks.

Recommended fix Moderate confidence

FortiADC 7.6.4 or later for 7.2.x/7.4.x/7.6.x branches; FortiADC 8.0.1 or later for 8.0.x branch

  1. 1. Identify current FortiADC version by navigating to Dashboard > System Information in the web UI or running: 'get system status' in CLI
  2. 2. For versions 7.2.x, 7.4.x, 7.6.0-7.6.3: Plan upgrade to version 7.6.4 or later
  3. 3. For version 8.0.0: Plan upgrade to version 8.0.1 or later (if available)
  4. 4. Backup current configuration via CLI: 'execute backup config tftp <config_name> <tftp_server_ip>' or via web UI: System > Maintenance > Backup & Restore
  5. 5. Download the appropriate firmware image from Fortinet Customer Support portal (https://support.fortinet.com)
  6. 6. Upload and install the firmware via web UI: System > Firmware or via CLI: 'execute system firmware upgrade'
  7. 7. After reboot, verify the new version: 'get system status' and confirm version matches the target fixed release
  8. 8. Test that the web interface functions normally and the XSS vulnerability is no longer present
Caveat Review Fortinet release notes for 7.6.4/8.0.1 for any configuration or behavioral changes; certain legacy features may be deprecated in major version upgrades

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

Fix this in Fortiadc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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