dbcve.org
FortindrApplication · Fortinet

CVE-2023-48790

HIGH · 8.8 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 7.0.6 / 7.1.2 or later.
See remediation →
95/100
Remediation priority · Urgent
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
A cross site request forgery vulnerability [CWE-352] in Fortinet FortiNDR version 7.4.0, 7.2.0 through 7.2.1 and 7.1.0 through 7.1.1 and before 7.0.5 may allow a remote unauthenticated attacker to execute unauthorized actions via crafted HTTP GET 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

A cross-site request forgery (CSRF) vulnerability in Fortinet FortiNDR versions 7.4.0, 7.2.0-7.2.1, 7.1.0-7.1.1, and before 7.0.5 allows remote unauthenticated attackers to execute unauthorized actions via crafted HTTP GET requests due to missing anti-CSRF tokens or proper referer validation on sensitive endpoints.

MitigationApply the vendor-supplied patch to upgrade to FortiNDR version 7.0.5 or later (or the fixed 7.2.x/7.4.x release) to implement proper CSRF token validation on state-changing GET endpoints.

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
FortindrApplication
Affected:>= 1.5.0, < 7.0.6>= 7.1.0, < 7.1.2>= 7.2.0, <= 7.2.2= 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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Confirm FortiNDR is installed
    Check for FortiNDR processes or service: on Linux run 'ps aux | grep -i fortindr' or check for /opt/fortindr directory; on the appliance console use 'show system status' to confirm the product name.
    Affected if FortiNDR is not found, the system is not affected by this CVE.
  2. Identify installed FortiNDR version
    Run 'get system status' via FortiNDR CLI or check the web UI dashboard for the firmware version number displayed as 'Version' or 'Firmware'.
    Affected if The version matches any of these ranges: >= 1.5.0 and < 7.0.6; >= 7.1.0 and < 7.1.2; >= 7.2.0 and <= 7.2.2; or equals 7.4.0.
  3. Determine if web management interface is accessible
    Attempt to reach the FortiNDR web UI over HTTPS on port 443 or the configured management port. Check firewall rules and interface bindings with 'show system interface' in CLI.
    Affected if The web interface is accessible from untrusted networks, increasing exposure to unauthenticated attack vectors.
  4. Inspect HTTP responses for anti-CSRF protection
    Capture an HTTP response from a state-changing endpoint (such as /api/v2.0/... or sensitive GET requests) using browser dev tools or curl. Examine headers and cookies for anti-CSRF tokens (e.g., CSRFToken, X-CSRF-Token) and the presence of Referer header validation.
    Affected if State-changing GET endpoints lack CSRF tokens in requests/cookies and do not validate the Referer header, indicating the vulnerability is present.

A system is affected if it runs FortiNDR versions 1.5.0 through 7.0.5, 7.1.0-7.1.1, 7.2.0-7.2.2, or exactly 7.4.0, and its sensitive GET endpoints lack anti-CSRF token validation.

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.0.6 / 7.1.2 or later
Fixed in 7.0.67.1.2
Interim mitigation

Apply the vendor-supplied patch to upgrade to FortiNDR version 7.0.5 or later (or the fixed 7.2.x/7.4.x release) to implement proper CSRF token validation on state-changing GET endpoints.

Recommended fix High confidence

FortiNDR 7.0.6 (for 7.0.x) or 7.1.2 (for 7.1.x) or 7.2.3 (for 7.2.x) or 7.4.1+ (for 7.4.0)

  1. 1. Identify the currently installed FortiNDR version using the web UI or CLI (execute 'get system status' in FortiNDR CLI)
  2. 2. Based on current version, determine the minimum fixed release to upgrade to: if running 7.0.x, upgrade to 7.0.6; if running 7.1.x, upgrade to 7.1.2; if running 7.2.x, upgrade to 7.2.3; if running 7.4.0, upgrade to 7.4.1 or later
  3. 3. Before upgrading, back up the FortiNDR configuration via web UI (System > Settings > Backup & Restore) or CLI ('execute backup full-config')
  4. 4. Download the appropriate firmware upgrade file from Fortinet support portal (support.fortinet.com) matching the target fixed version
  5. 5. Upload and install the firmware via FortiNDR web UI (System > Firmware > Upload) or CLI ('execute system firmware upgrade <image-file>')
  6. 6. After upgrade completes, verify the new version is installed and the vulnerability is resolved by checking 'get system status' output
  7. 7. Confirm all expected services and configurations are operational post-upgrade
Caveat Review Fortinet release notes for the target version to check for any configuration or feature changes that may affect existing deployments; always test in non-production first

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

Fix this in Fortindr Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,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 $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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