dbcve.org
Pdf EditorApplication · Foxit

CVE-2026-3780

HIGH · 7.8 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to after 2025.3.0.35737 or later.
See remediation →
81/100
Remediation priority · High
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
The application's installer runs with elevated privileges but resolves system executables and DLLs using untrusted search paths that can include user-writable directories, allowing a local attacker to place malicious binaries with the same names and have them loaded or executed instead of the legitimate system files, resulting in local privilege escalation.

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

The installer for this application runs with elevated (administrator/SYSTEM) privileges but uses untrusted search paths to locate system executables and DLLs, allowing it to inadvertently load malicious binaries from user-writable directories instead of legitimate system files, achieving local privilege escalation.

MitigationFix the installer to use secure, absolute paths or whitelist-based path resolution for all executables and DLLs, removing user-writable directories from the search order.

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
Pdf EditorApplication
Affected:<= 13.2.2.24014>= 14.0.0.33046, <= 14.0.2.33402>= 2023.1.0.15510, <= 2023.3.0.23028>= 2024.1.0.23997, <= 2024.4.1.27687>= 2025.1.0.27937, <= 2025.3.0.35737
Pdf ReaderApplication
Affected:<= 2025.3.0.35737

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

CVSS:3.1/AV:L/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. Check if Foxit PDF Editor is installed
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or HKEY_LOCAL_MACHINE\SOFTWARE\FoxitSoftware\Foxit PDF Editor. Alternatively, check common install directories such as C:\Program Files\Foxit PDF Editor or C:\Program Files (x86)\Foxit PDF Editor.
    Affected if Foxit PDF Editor is found on the system
  2. Determine installed Foxit PDF Editor version
    In the Registry uninstall key or FoxitSoftware key, locate the DisplayVersion or Version string. If using the GUI, right-click the Foxit PDF Editor shortcut, select Properties, and check the Details tab for Product Version.
    Affected if The installed version falls within any of these ranges: <= 13.2.2.24014, >= 14.0.0.33046 and <= 14.0.2.33402, >= 2023.1.0.15510 and <= 2023.3.0.23028, >= 2024.1.0.23997 and <= 2024.4.1.27687, or >= 2025.1.0.27937 and <= 2025.3.0.35737
  3. Check if Foxit PDF Reader is installed and its version
    Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for Foxit PDF Reader entry, or check C:\Program Files\Foxit PDF Reader directory. Locate the version in DisplayVersion.
    Affected if Foxit PDF Reader version is <= 2025.3.0.35737
  4. Verify if installer has been executed on the system
    Check for recent installer activity: review Windows Event Viewer Application logs for Foxit installer events, look for FoxitSetup*.exe in recent file access locations, or check %TEMP% folder for installer extraction logs. Also examine C:\ProgramData\Foxit\ for installer logs.
    Affected if The Foxit installer has been run on this system while running with administrator or SYSTEM privileges
  5. Confirm installer search path vulnerability exposure
    Examine the installed Foxit application directory for any unexpected DLLs or executables in user-writable locations that may have been dropped by a malicious installer. Compare file timestamps against known installer execution dates.
    Affected if Unexpected binaries appear in the Foxit install directory or system directories with timestamps coinciding with installer execution, suggesting DLL hijacking occurred

A system is affected if Foxit PDF Editor (any version within the listed ranges) or Foxit PDF Reader (version <= 2025.3.0.35737) has been installed using the vulnerable installer, and that installer was executed with elevated privileges.

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.

From vendor data
Upgrade available Upgrade to a release after 2025.3.0.35737
Interim mitigation

Fix the installer to use secure, absolute paths or whitelist-based path resolution for all executables and DLLs, removing user-writable directories from the search order.

Fix this in Pdf Editor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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