dbcve.org
FortisoarApplication · Fortinet

CVE-2025-32932

MEDIUM · 5.4 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 7.5.2 / 7.6.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 neutralization of input during web page generation ('cross-site scripting') vulnerability [CWE-79] in FortiSOAR version 7.6.1 and below, version 7.5.1 and below, 7.4 all versions, 7.3 all versions, 7.2 all versions, 7.0 all versions, 6.4 all versions WEB UI may allow an authenticated remote attacker to perform an XSS attack via stored malicious service 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 · moderate confidence

A stored cross-site scripting (XSS) vulnerability in FortiSOAR's web UI allows authenticated attackers to inject malicious JavaScript through service requests. The malicious payload persists in the system and executes when other users view the affected content.

MitigationUpgrade FortiSOAR to the patched version (7.6.2 or later). Until upgrade, implement output encoding and input validation on all service request fields in the web UI.

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
FortisoarApplication
Affected:>= 6.4.0, < 7.5.2>= 7.6.0, < 7.6.2

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

CVSS:3.1/AV:N/AC:L/PR:L/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 FortiSOAR installation
    Locate the FortiSOAR application in your environment. This is typically a web-based application running on a dedicated server or virtual appliance. Check for the FortiSOAR web interface by accessing the URL (commonly https://<hostname>/fras/ or the configured endpoint).
    Affected if FortiSOAR web UI is accessible and running in your environment.
  2. Check installed FortiSOAR version
    Log into the FortiSOAR web UI as an administrator. Navigate to the Settings or System Configuration section, typically found under the user profile or admin menu. Locate the version information typically displayed as 'Version' or 'About' which shows the full version number.
    Affected if The installed version falls within the affected ranges: 6.4.0 through 7.5.1, or 7.6.0 through 7.6.1.
  3. Verify web UI service request module is enabled
    In the FortiSOAR administration panel, navigate to the module configuration or playbooks/settings area. Look for the 'Service Requests' or 'SRTasking' module settings. Confirm this module is listed as active or enabled in the system configuration.
    Affected if The Service Request (SRTasking) module is enabled and accessible to authenticated users in the web UI.
  4. Inspect service request records for suspicious content
    Access the Service Requests or SRTasking section in the FortiSOAR web UI as an administrator. Browse through existing service request records, particularly in text fields such as name, description, or request parameters. Look for unusual characters, HTML tags, or JavaScript code patterns like <script>, javascript:, onload, or other scriptable elements.
    Affected if Service request records contain unsanitized HTML, script tags, or JavaScript code in input fields that would execute when viewed by other users.

You are affected if FortiSOAR with a version in 6.4.0 to 7.5.1 or 7.6.0 to 7.6.1 is running, the web UI service request module is enabled, and service request fields contain unescaped malicious scripts.

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.5.2 / 7.6.2 or later
Fixed in 7.5.27.6.2
Interim mitigation

Upgrade FortiSOAR to the patched version (7.6.2 or later). Until upgrade, implement output encoding and input validation on all service request fields in the web UI.

Recommended fix High confidence

FortiSOAR 7.5.2 or later (7.5.x branch); FortiSOAR 7.6.2 or later (7.6.x branch)

  1. 1. Identify the currently installed FortiSOAR version by navigating to the FortiSOAR UI dashboard or checking the system information.
  2. 2. If running version 7.5.x (6.4.0 <= version < 7.5.2): Plan an upgrade to version 7.5.2 or later in the 7.5 branch.
  3. 3. If running version 7.6.0 or 7.6.1: Plan an upgrade to version 7.6.2 or later in the 7.6 branch.
  4. 4. Before upgrading, backup the FortiSOAR database and configuration following standard backup procedures.
  5. 5. Review FortiSOAR upgrade documentation for your specific version jump to ensure compatibility.
  6. 6. Perform the upgrade during a planned maintenance window to minimize business impact.
  7. 7. After upgrade, verify the FortiSOAR version reflects the patched release (7.5.2+ or 7.6.2+).
  8. 8. Test that the web UI functions correctly post-upgrade.
Caveat Upgrade between major versions may require migration steps; review FortiSOAR release notes for breaking changes before proceeding

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

Fix this in Fortisoar Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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