FortisoarApplication · Fortinet
CVE-2023-25605
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 · uneditedA improper access control vulnerability in Fortinet FortiSOAR 7.3.0 - 7.3.1 allows an attacker authenticated on the administrative interface to perform unauthorized actions via crafted HTTP 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 confidenceFortiSOAR versions 7.3.0 through 7.3.1 contain an improper access control vulnerability in the administrative interface. An authenticated attacker can craft HTTP requests to perform unauthorized actions, bypassing intended authorization checks despite having valid authentication.
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
>= 7.3.0, < 7.3.2CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify FortiSOAR versionAccess the FortiSOAR administrative interface and navigate to the System Administration or About page to view the installed version. Alternatively, use the CLI command 'system version' or 'fortisoar --version' if available.Affected if The installed version is 7.3.0, 7.3.1, or any version >= 7.3.0 and < 7.3.2
-
Confirm admin interface exposureDetermine whether the FortiSOAR administrative interface is accessible from the network. Review firewall rules, reverse proxy configurations, or VPN settings that control access to port 443 or the FortiSOAR web portal.Affected if The administrative interface is reachable from untrusted networks or the internet without proper network segmentation
-
Review authentication logsExamine FortiSOAR audit logs, access logs, or security logs for the affected timeframe. Look for successful authentication events followed by API calls or administrative actions that the user role should not permit.Affected if Logs show authenticated users performing actions outside their assigned role permissions, or unexpected administrative operations from standard user accounts
You are affected if FortiSOAR version is 7.3.0 or 7.3.1 and the admin interface is accessible to authenticated users who may have exploited the authorization bypass.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.3.2
Apply the vendor-supplied patch or upgrade to a FortiSOAR version beyond 7.3.1. Review administrative access logs for indicators of exploitation and audit role-based access control configurations.
FortiSOAR 7.3.2
- Verify current FortiSOAR version by navigating to the Adminstration > System > About page in the FortiSOAR UI
- Review the FortiSOAR 7.3.2 release notes for new features, resolved issues, and any special upgrade instructions
- Create a complete backup of the FortiSOAR database and configuration
- Create a snapshot or backup of the FortiSOAR virtual machine or physical appliance
- If running a distributed architecture, identify and document all connected nodes
- Follow Fortinet's standard upgrade procedure: navigate to Adminstration > System > Upgrade in the FortiSOAR UI, or use the command line csf CLI tool
- Upload the FortiSOAR 7.3.2 upgrade package and initiate the upgrade
- Monitor the upgrade process and verify all services restart successfully
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortisoar
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25605 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-25605 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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