dbcve.org
Fortidlp AgentApplication · Fortinet

CVE-2025-53950

MEDIUM · 6.0 CVSS v3.1 Published 2025-10-16
Fix available
A fix is available. Upgrade to after 11.5.1 or later.
See remediation →
62/100
Remediation priority · Elevated
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 Exposure of Private Personal Information ('Privacy Violation') vulnerability [CWE-359] in Fortinet FortiDLP Agent's Outlookproxy plugin for MacOS and 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 administrator to collect current user's email information.

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 a privacy violation (CWE-359) in FortiDLP Agent's Outlookproxy plugin on MacOS and Windows. The vulnerability allows an authenticated administrator to collect the current user's email information, exposing private personal data that should not be accessible even to administrators.

MitigationUpgrade FortiDLP Agent to the latest patched version provided by Fortinet. Review and audit administrator access controls to ensure proper separation of duties and limit email data collection to only necessary administrative functions.

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

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/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. Check installed FortiDLP Agent version
    On Windows, open Programs and Features or run 'reg query "HKLM\SOFTWARE\Fortinet\FortiDLP Agent" /v Version'. On MacOS, run 'defaults read /Applications/FortiDLP\ Agent.app/Contents/Info CFBundleShortVersionString' or check via the FortiDLP console.
    Affected if The installed version is 10.3.1 through 11.5.1 inclusive, meaning the version falls within the affected range.
  2. Verify Outlookproxy plugin is loaded
    Check if the Outlookproxy plugin is present and enabled. On Windows, look in the FortiDLP Agent installation directory (typically C:\Program Files\Fortinet\FortiDLP Agent\) for an outlookproxy.dll or similar module. On MacOS, check /Applications/FortiDLP Agent.app/Contents/PlugIns/ for the outlookproxy component.
    Affected if The Outlookproxy plugin file exists and is loaded by the FortiDLP Agent, which is required for the vulnerability to be exploitable.
  3. Review administrator email access policies
    Access the FortiDLP administrative console and review policies related to Outlook/email monitoring. Look for any policies that grant administrators access to user email data, specifically the 'email content' or 'email metadata' collection features within the Outlookproxy configuration.
    Affected if Policies are configured that allow administrators to access or export user email information through the FortiDLP console.
  4. Inspect audit logs for administrator email data access
    In the FortiDLP console, review administrative audit logs for events involving 'email_read', 'email_export', or similar actions performed by administrators on the Outlookproxy plugin. Check if any administrator accounts have accessed user email data.
    Affected if Audit logs show administrator accounts have accessed or retrieved user email content or metadata through the Outlookproxy plugin.

A user is affected if their FortiDLP Agent version is between 10.3.1 and 11.5.1 inclusive AND the Outlookproxy plugin is enabled, allowing administrators to access user email data that should be restricted.

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

Upgrade FortiDLP Agent to the latest patched version provided by Fortinet. Review and audit administrator access controls to ensure proper separation of duties and limit email data collection to only necessary administrative functions.

Recommended fix Moderate confidence

FortiDLP Agent 11.6.0 or later (the first release after 11.5.1 that addresses this privacy violation)

  1. 1. Identify the current FortiDLP Agent version installed on affected MacOS and Windows systems
  2. 2. Navigate to the FortiDLP admin console or use the appropriate management interface
  3. 3. Schedule an upgrade to FortiDLP Agent version 11.6.0 or later, which contains the fix for this vulnerability
  4. 4. Verify the upgrade was successful by checking the agent version in the admin console
  5. 5. Confirm the Outlookproxy plugin is functioning correctly after the upgrade
Caveat Review FortiDLP release notes for any compatibility changes between your current version and 11.6.0+ before upgrading

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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