CVE-2026-57239: CVE-2026-57239: The user-controllable executable files will be directly executed by high-privilege process…
foxit · pdf editor · NVD published 2026-07-08 · posted 2026-07-08 · last modified 2026-07-09
What it is
The user-controllable executable files will be directly executed by high-privilege processes, allowing low-privilege users to have the opportunity to elevate their privileges to NT AUTHORITY\SYSTEM.
| Weakness | CWE-427 |
|---|---|
| CVSS vector | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (source: [email protected]) |
| ATT&CK tactics | Execution → Stealth |
Exploitation evidence
First exploit evidence seen: 2026-07-08 (earliest date across the sources below).
Exploited in the wild
No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).
Public exploit code
GitHub proof-of-concept repositories
1 public repositories from 1 accounts, first seen 2026-07-08. Most starred: Paradoxis/CVE-2026-57239 (16 stars), view repository.
Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.
Sources: nomi-sec/PoC-in-GitHub.
How to fix it
Fixed versions
- foxit pdf editor: versions up to and including 13.2.4.24048 are affected; check the vendor advisory for the fixed release.
- foxit pdf editor: versions up to and including 14.0.4.33508 are affected; check the vendor advisory for the fixed release.
- foxit pdf editor: versions up to and including 2023.3.0.23028 are affected; check the vendor advisory for the fixed release.
- foxit pdf editor: versions up to and including 2024.4.1.27687 are affected; check the vendor advisory for the fixed release.
- foxit pdf editor: versions up to and including 2025.3.0.35737 are affected; check the vendor advisory for the fixed release.
- foxit pdf editor: versions up to and including 2026.1.1.36485 are affected; check the vendor advisory for the fixed release.
- foxit pdf reader: versions up to and including 2026.1.1.36485 are affected; check the vendor advisory for the fixed release.
Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.
Vendor advisories and patches
- https://www.foxit.com/support/security-bulletins.html (Vendor Advisory)
MITRE ATT&CK mitigations for this chain
- M1038 Execution Prevention (for T1574.001) : Identify and block potentially malicious software executed through DLL hijacking by using application control solutions capable of blocking DLLs loaded by legitimate software.
- M1044 Restrict Library Loading (for T1574.001) : Disallow loading of remote DLLs. This is included by default in Windows Server 2012+ and is available by patch for XP+ and Server 2003+. Enable Safe DLL Search Mode to move the user's current folder later in the search order. This is included by default in modern versions of Windows; the associated Windows Registry ke
- M1051 Update Software (for T1574.001) : Update software regularly to include patches that fix DLL side-loading vulnerabilities.
- M1047 Audit (for T1574.001) : Use auditing tools capable of detecting DLL search order hijacking opportunities on systems within an enterprise and correct them. Toolkits like the PowerSploit framework contain PowerUp modules that can be used to explore systems for DLL hijacking weaknesses. Use the program `sxstrace.exe` that is included with Windo
- M1013 Application Developer Guidance (for T1574.001) : When possible, include hash values in manifest files to help prevent side-loading of malicious libraries.
Detection Generic guidance
- Execution: Watch for the service process spawning shells or script interpreters (cmd.exe, powershell, sh, bash, python) via EDR process-tree rules.
Response checklist Generic guidance
- Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
- Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
- Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
- Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.