dbcve.org
Fortidlp AgentApplication · Fortinet

CVE-2025-53951

HIGH · 7.8 CVSS v3.1 Published 2025-10-16
Fix available
A fix is available. Upgrade to after 11.5.1 or later.
See remediation →
80/100
Remediation priority · High
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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability [CWE-22] in Fortinet FortiDLP Agent's Outlookproxy plugin for Windows 11.5.1 and 11.4.2 through 11.4.6 and 11.3.2 through 11.3.4 and 11.2.0 through 11.2.3 and 11.1.1 through 11.1.2 and 11.0.1 and 10.5.1 and 10.4.0, and 10.3.1 may allow an authenticated attacker to escalate their privilege to LocalService via sending a crafted request to a local listening port.

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 path traversal vulnerability in FortiDLP Agent's Outlookproxy plugin allows an authenticated attacker to escape restricted directories by sending crafted requests to a local listening port, achieving privilege escalation to LocalService.

MitigationUpdate FortiDLP Agent to the patched version provided by Fortinet. If immediate patching is not possible, restrict local access to trusted authenticated users and monitor the local listening port for anomalous requests.

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
Fortidlp AgentApplication
Affected:>= 10.3.1, <= 11.5.1

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

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

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

  1. Identify FortiDLP Agent installation and version
    Check installed programs on the system, or run: 'fortiddlp-agent --version' or check registry under HKLM\SOFTWARE\Fortinet\FortiDLP\Agent for the Version value
    Affected if The installed version falls within range 10.3.1 to 11.5.1 inclusive
  2. Confirm Outlookproxy plugin is present
    Examine FortiDLP configuration files or registry keys for the Outlookproxy plugin component. Check installation directory for outlookproxy.dll or related module, or look for 'Outlookproxy' in FortiDLP config files
    Affected if The Outlookproxy plugin is installed or enabled in the FortiDLP configuration
  3. Identify local listening port for Outlookproxy service
    Run 'netstat -an | findstr LISTENING' or use Process Explorer to identify ports bound by FortiDLP processes. Check FortiDLP service documentation or configuration for the Outlookproxy listening port (typically a local high port)
    Affected if A local port associated with Outlookproxy is in LISTENING state and accepts connections
  4. Verify access control on the local listening port
    Use accesschk or icacls to check which users can connect to the identified FortiDLP listening port. Attempt a connection from a low-privilege account to confirm accessibility
    Affected if Unprivileged or unauthenticated users can connect to the local FortiDLP listening port used by Outlookproxy

You are affected if FortiDLP Agent version is between 10.3.1 and 11.5.1 inclusive AND the Outlookproxy plugin is enabled with an accessible local listening port that accepts connections from lower-privilege 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 a release after 11.5.1
Interim mitigation

Update FortiDLP Agent to the patched version provided by Fortinet. If immediate patching is not possible, restrict local access to trusted authenticated users and monitor the local listening port for anomalous requests.

Recommended fix Moderate confidence

FortiDLP Agent version 11.5.2 or later (confirm via fortiguard.fortinet.com)

  1. Contact Fortinet support or visit fortiguard.fortinet.com to confirm the availability of FortiDLP Agent version 11.5.2 or later, which should contain the fix for this vulnerability
  2. Verify the current installed version of FortiDLP Agent on affected Windows systems
  3. Plan an upgrade to the confirmed fixed version, ensuring compatibility with your environment
  4. Test the upgrade in a staging environment before deploying to production systems
  5. Deploy the upgrade to all affected Windows endpoints running FortiDLP Agent
Caveat Review Fortinet release notes for any compatibility or configuration changes between your current version and the fixed version

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

Fix this in Fortidlp Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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