dbcve.org
Pdf EditorApplication · Foxit

CVE-2026-5942

MEDIUM · 5.5 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 →
58/100
Remediation priority · Elevated
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
Flaws in page lifecycle management allow document structure changes to desynchronize internal component states, causing subsequent operations to access invalidated objects and crash the program.

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

Flaws in page lifecycle management cause document structure changes to desynchronize internal component states, leading to subsequent operations accessing invalidated objects and crashing the program. This appears to be a memory safety issue similar to use-after-free where object references become stale after document modifications.

MitigationImplement proper state synchronization and reference tracking in page/document lifecycle management; validate object states before operations and ensure cleanup handlers properly invalidate references when document structure changes.

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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. Confirm Foxit PDF product is installed
    Open Windows Control Panel > Programs and Features, or check C:\Program Files\Foxit Software for executable files (Foxit PDF Editor.exe or Foxit Reader.exe)
    Affected if Either Foxit PDF Editor or Foxit PDF Reader is present on the system
  2. Locate the installed executable
    Find the main executable: Foxit PDF Editor.exe (typically in C:\Program Files\Foxit Software\Foxit PDF Editor\) or Foxit Reader.exe (typically in C:\Program Files\Foxit Software\Foxit Reader\)
    Affected if The executable exists on the system
  3. Determine the exact version number
    Right-click the executable, select Properties, go to the Details tab, and read the Product version field. Alternatively, open the application and navigate to Help > About Foxit [Product Name]
    Affected if Version cannot be determined or is not visible
  4. Compare version against affected ranges
    For Foxit PDF Editor: check if version is < 13.2.4, OR >= 14.0.0 AND < 14.0.0.4, OR >= 2023.0.0 AND < 2026.1.1. For Foxit PDF Reader: check if version is < 2026.1.1
    Affected if Installed version falls into any of the vulnerable ranges: Editor < 13.2.4; Editor 14.0.0-14.0.0.3; Editor 2023.0.0-2026.1.0; Reader < 2026.1.1

The environment is affected if Foxit PDF Editor or Reader is installed with a version number below the fixed releases (13.2.4, 14.0.0.4, or 2026.1.1 depending on the release track).

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 state synchronization and reference tracking in page/document lifecycle management; validate object states before operations and ensure cleanup handlers properly invalidate references when document structure changes.

Recommended fix High confidence

Pdf Editor: upgrade to 13.2.4, 14.0.4, or 2026.1.1 (depending on current version); Pdf Reader: upgrade to 2026.1.1

  1. Identify the currently installed Foxit product (Pdf Editor or Pdf Reader) and its exact version number
  2. Determine which version range your current installation falls into based on the affected versions listed
  3. Navigate to the official Foxit website at www.foxit.com to download the appropriate fixed version
  4. For Pdf Editor: If your version is < 13.2.4, download version 13.2.4 or later; if >= 14.0.0 and < 14.0.4, download version 14.0.4 or later; if >= 2023.0.0 and < 2026.1.1, download version 2026.1.1 or later
  5. For Pdf Reader: If your version is < 2026.1.1, download version 2026.1.1 or later
  6. Uninstall the current version of the Foxit software
  7. Install the newly downloaded fixed version
  8. Verify the installed version matches the expected fixed release

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

Fix this in Pdf Editor Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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