dbcve.org
Pdf EditorApplication · Foxit

CVE-2026-5943

HIGH · 7.8 CVSS v3.1 Published 2026-04-27
Fix available
A fix is available. Upgrade to 13.2.4 / 14.0.4 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
Document structural anomalies caused inconsistencies between page element relationships and internal index states. When scripts triggered document modifications, object reference validity was not properly maintained, leading to a crash when accessing an invalid pointer during page information queries.

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 · moderate confidence

A dangling pointer vulnerability exists where document modifications triggered by scripts cause internal index states to become inconsistent with page element relationships. Object references are not properly maintained, leading to invalid pointer access and crash during page information queries.

MitigationImplement proper object reference lifecycle management during document modifications, including validation checks before pointer dereference and ensuring index synchronization with element relationships.

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.4>= 14.0.0, < 14.0.4>= 2023.0.0, < 2026.1.1
Pdf ReaderApplication
Affected:< 2026.1.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
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. Identify if Foxit PDF Editor or Reader is installed
    On Windows, check the registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Foxit' or look in C:\Program Files\Foxit. On macOS, check /Applications for Foxit PDF Editor.app or Foxit PDF Reader.app.
    Affected if Foxit PDF Editor or Reader software is found on the system
  2. Determine the installed version of Foxit PDF Editor
    Open Foxit PDF Editor, click Help > About Foxit PDF Editor, or on Windows check the registry value 'DisplayVersion' under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{Foxit GUID}
    Affected if The version number returned is less than 13.2.4, OR is 14.0.0, 14.0.1, 14.0.2, or 14.0.3, OR is between 2023.0.0 and 2026.1.0 inclusive
  3. Determine the installed version of Foxit PDF Reader
    Open Foxit PDF Reader, click Help > About Foxit PDF Reader, or on Windows check the registry value 'DisplayVersion' under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{Foxit Reader GUID}
    Affected if The version number returned is less than 2026.1.1
  4. Confirm the vulnerable feature is reachable
    The vulnerability is triggered when scripts cause document modifications that affect internal page element indexes. Test by opening a PDF with JavaScript actions that modify the document structure, then attempt to query page information.
    Affected if The application crashes when performing page information queries after script-triggered document modifications

A user is affected if Foxit PDF Editor version is less than 13.2.4, or between 14.0.0 and 14.0.3, or between 2023.0.0 and 2026.1.0; or if Foxit PDF Reader version is less than 2026.1.1.

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 13.2.4 / 14.0.4 / 2026.1.1 or later
Fixed in 13.2.414.0.42026.1.1
Interim mitigation

Implement proper object reference lifecycle management during document modifications, including validation checks before pointer dereference and ensuring index synchronization with element relationships.

Recommended fix High confidence

Pdf Editor: 13.2.4 (for <13.2.4), 14.0.4 (for >=14.0.0,<14.0.4), or 2026.1.1 (for >=2023.0.0,<2026.1.1); Pdf Reader: 2026.1.1

  1. 1. Identify the installed Foxit product (Pdf Editor or Pdf Reader) and current version via Help > About
  2. 2. For Pdf Editor: If version < 13.2.4, upgrade to version 13.2.4 or later
  3. 3. For Pdf Editor: If version >= 14.0.0 and < 14.0.4, upgrade to version 14.0.4 or later
  4. 4. For Pdf Editor: If version >= 2023.0.0 and < 2026.1.1, upgrade to version 2026.1.1 or later
  5. 5. For Pdf Reader: If version < 2026.1.1, upgrade to version 2026.1.1 or later
  6. 6. Download the appropriate fixed version from the official Foxit website at www.foxit.com
  7. 7. Close all Foxit applications before running the installer
  8. 8. Run the installer and follow the prompts to complete the upgrade
Caveat Standard minor version upgrades typically retain settings; however, test critical documents after upgrade to confirm compatibility

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

Fix this in Pdf Editor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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