dbcve.org
FortisiemApplication · Fortinet

CVE-2026-25972

MEDIUM · 6.1 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 7.3.5 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 improper neutralization of input during web page generation ('cross-site scripting') vulnerability in Fortinet FortiSIEM 7.4.0, FortiSIEM 7.3.0 through 7.3.4 may allow a remote unauthenticated attacker to provide arbitrary data enabling a social engineering attack via spoofed URL parameters.

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 cross-site scripting (XSS) vulnerability in Fortinet FortiSIEM versions 7.4.0 and 7.3.0-7.3.4 where user-supplied input in URL parameters is not properly neutralized during web page generation. An unauthenticated remote attacker can craft malicious URLs with spoofed parameters to inject arbitrary script into pages viewed by other users, facilitating social engineering attacks.

MitigationUpgrade FortiSIEM to the vendor-provided patched version. As an interim measure, implement URL input validation and output encoding at any web application firewall or proxy layer.

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
FortisiemApplication
Affected:>= 7.3.0, < 7.3.5= 7.4.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 FortiSIEM version
    Log into the FortiSIEM web interface and navigate to Admin > System Settings > System > About, or run 'ph status' command from CLI to display the version information.
    Affected if The displayed version matches 7.4.0 or falls within 7.3.0 through 7.3.4 inclusive.
  2. Confirm web interface is accessible
    Determine if the FortiSIEM web UI port (typically 443 or 8080) is listening and reachable. Use netstat or curl to verify the web service responds to HTTP/HTTPS requests.
    Affected if The web interface is exposed and responds to requests, making the XSS vector reachable.
  3. Test URL parameter reflection
    Craft a test URL with a benign XSS payload in a parameter (for example, appending '?test=<script>alert(1)</script>' to the FortiSIEM login page or common endpoints). Observe whether the script tags appear unmodified in the page source or are executed.
    Affected if The payload is reflected as-is in the response without HTML encoding or sanitization, indicating the vulnerability is present.
  4. Review web request logs
    Examine FortiSIEM or upstream proxy/waf logs for any attempts to inject script content via URL parameters. Look for patterns containing '<script>', 'javascript:', or other HTML event handlers in query strings.
    Affected if Log entries show URL parameters containing unsanitized script content reaching the application.

You are affected if FortiSIEM version is 7.4.0 or between 7.3.0 and 7.3.4, and the web interface is accessible and reflects URL parameters without encoding.

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.3.5 or later
Fixed in 7.3.5
Interim mitigation

Upgrade FortiSIEM to the vendor-provided patched version. As an interim measure, implement URL input validation and output encoding at any web application firewall or proxy layer.

Recommended fix Moderate confidence

FortiSIEM 7.3.5 or later (for 7.3.x versions); FortiSIEM 7.4.1 or later (for 7.4.0)

  1. 1. Identify the current FortiSIEM version using the web UI or CLI (show system status)
  2. 2. For versions 7.3.0 through 7.3.4: Plan upgrade to FortiSIEM 7.3.5 or later
  3. 3. For version 7.4.0: Plan upgrade to FortiSIEM 7.4.1 or later (if available) or 7.3.5+
  4. 4. Review FortiSIEM upgrade prerequisites and backup configuration before proceeding
  5. 5. Perform the upgrade following Fortinet's official upgrade documentation
  6. 6. After upgrade, verify the system is operational and the XSS vulnerability is resolved
  7. 7. Validate the fix by checking that URL parameters are properly sanitized in the web interface
Caveat Review FortiSIEM release notes for any breaking changes between versions before upgrading

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

Fix this in Fortisiem Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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