dbcve.org
FortisoarApplication · Fortinet

CVE-2025-59810

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 7.5.2 / 7.6.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 access control vulnerability in Fortinet FortiSOAR PaaS 7.6.0 through 7.6.2, FortiSOAR PaaS 7.5.0 through 7.5.1, FortiSOAR PaaS 7.4 all versions, FortiSOAR PaaS 7.3 all versions, FortiSOAR on-premise 7.6.0 through 7.6.2, FortiSOAR on-premise 7.5.0 through 7.5.1, FortiSOAR on-premise 7.4 all versions, FortiSOAR on-premise 7.3 all versions may allow information disclosure to an authenticated attacker via crafted 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 confidence

This is an improper access control vulnerability in Fortinet FortiSOAR (both PaaS and on-premise) affecting versions 7.3 through 7.6.2. An authenticated attacker can craft specific requests to bypass access controls and disclose sensitive information that should be restricted based on the user's role or permissions.

MitigationApply vendor-provided patches or upgrade to the latest FortiSOAR version. Additionally, audit user roles and permissions to ensure least-privilege access is enforced.

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:>= 7.3.0, < 7.5.2>= 7.6.0, < 7.6.3

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify FortiSOAR installed version
    Log into FortiSOAR as an administrator and navigate to the About page (Settings > System > About) or use the API endpoint /api/info/ to retrieve the version number
    Affected if The reported version falls within 7.3.0 - 7.5.1 or 7.6.0 - 7.6.2
  2. Verify FortiSOAR web interface accessibility
    Attempt to reach the FortiSOAR login page via HTTPS on the configured host and port (default 443)
    Affected if The FortiSOAR web interface is reachable from a network where potential attackers could authenticate
  3. Confirm authentication is enabled
    Check that local user authentication or SSO integration is active in Settings > Users & Roles > Authentication
    Affected if User authentication is enabled and valid user accounts exist in the system
  4. Audit role-based access control configuration
    Review user roles and permissions in Settings > Users & Roles > Roles to identify if any roles permit access to sensitive modules or data
    Affected if Roles with elevated permissions or access to sensitive data are assigned to non-admin users

You are affected if FortiSOAR version is 7.3.0 through 7.5.1 or 7.6.0 through 7.6.2 AND the web interface is accessible to authenticated users.

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.3 or later
Fixed in 7.5.27.6.3
Interim mitigation

Apply vendor-provided patches or upgrade to the latest FortiSOAR version. Additionally, audit user roles and permissions to ensure least-privilege access is enforced.

Recommended fix High confidence

FortiSOAR 7.5.2 or later, or FortiSOAR 7.6.3 or later (depending on your target branch)

  1. 1. Identify the currently installed FortiSOAR version by checking the About section in the FortiSOAR UI or running the command: csadm --version
  2. 2. If running version 7.3.x or 7.4.x, plan migration to version 7.5.2 or later (or 7.6.3 or later)
  3. 3. If running version 7.5.0-7.5.1, upgrade to FortiSOAR version 7.5.2 or later
  4. 4. If running version 7.6.0-7.6.2, upgrade to FortiSOAR version 7.6.3 or later
  5. 5. Before upgrading, perform a complete backup of the FortiSOAR database and configuration
  6. 6. Review Fortinet's upgrade documentation and release notes for the target version
  7. 7. Execute the upgrade following Fortinet's standard upgrade procedure for FortiSOAR
  8. 8. After upgrade, verify the system is operational and test that the access control vulnerability is remediated
Caveat Review release notes for any configuration or functionality changes between your current version and the target version before upgrading

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

Fix this in Fortisoar Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
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,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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