dbcve.org
FortisoarApplication · Fortinet

CVE-2025-59808

MEDIUM · 6.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 7.5.2 or later.
See remediation →
74/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 unverified password change vulnerability [CWE-620] 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 an attacker who has already gained access to a victim's user account to reset the account credentials without being prompted for the account's password

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

An unverified password change vulnerability (CWE-620) in FortiSOAR allows an authenticated attacker who already has access to a victim's user account to reset account credentials without being prompted for the current password. This bypasses a critical verification step in the password change workflow.

MitigationApply the vendor patch for FortiSOAR to address the missing password verification in the credential reset mechanism. Monitor account modification logs for unauthorized password changes until the patch is deployed.

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H

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 - typically accessed via web UI on port 443 or via the csadm CLI tool installed on the server. Run 'csadm --version' or check the web interface login page for version information.
    Affected if FortiSOAR is installed and the version falls within 7.3.0 to 7.5.1, or 7.6.0 to 7.6.3
  2. Verify the installed version
    Access the FortiSOAR administration panel or run the command line tool to retrieve the exact version number. Compare this against the affected ranges: 7.3.0 to less than 7.5.2, or 7.6.0 to 7.6.3.
    Affected if The installed version is any of: 7.3.0 through 7.5.1, or 7.6.0 through 7.6.3
  3. Review audit logs for password changes
    Access FortiSOAR audit logs (typically found under Configuration > Audit Logs in the web UI or via the API endpoint /api/audit). Search for events related to user password modifications or credential resets.
    Affected if Password change events exist for accounts where the current user session did not provide the existing password as verification
  4. Check user account modification events
    Examine the audit trail for user profile updates, specifically look for events indicating password resets performed by users who already had authenticated access to the target account.
    Affected if Password reset events show that an authenticated user modified another user's credentials without a password verification step being recorded

You are affected if FortiSOAR version is 7.3.0-7.5.1 or 7.6.0-7.6.3 and password changes occurred without verification of the old password.

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 or later
Fixed in 7.5.2
Interim mitigation

Apply the vendor patch for FortiSOAR to address the missing password verification in the credential reset mechanism. Monitor account modification logs for unauthorized password changes until the patch is deployed.

Recommended fix High confidence

FortiSOAR 7.5.2 or later; FortiSOAR 7.6.3 or later

  1. Identify your current FortiSOAR version by checking the system information in the FortiSOAR UI or via CLI
  2. Determine if you are on the 7.3.x, 7.4.x, 7.5.x, or 7.6.x branch
  3. If on 7.3.x or 7.4.x: Plan migration to either the 7.5.2+ or 7.6.3+ release branch
  4. If on 7.5.0-7.5.1: Upgrade to FortiSOAR 7.5.2 or later
  5. If on 7.6.0-7.6.2: Upgrade to FortiSOAR 7.6.3 or later
  6. Before upgrading, perform a full backup of the FortiSOAR database and configuration
  7. Review Fortinet release notes for upgrade prerequisites and compatibility requirements
  8. Execute the upgrade following Fortinet's documented upgrade procedure for FortiSOAR
Caveat Review release notes for any configuration or feature changes between your current version and 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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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