CVE-2026-57243
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 · uneditedDuring the process of page opening and form formatting, a JavaScript reentrancy results in an inconsistent document status. Subsequently, with outdated page information, the application attempts to access invalid addresses, causing the application to crash.
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 confidenceA JavaScript reentrancy vulnerability during page opening and form formatting causes document state inconsistency. When the application attempts to access memory using outdated/stale page information, it accesses invalid addresses, causing a crash (denial of service).
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<= 13.2.4.24048>= 14.0.0.33046, <= 14.0.4.33508>= 2023.1.0.15510, <= 2023.3.0.23028>= 2024.1.0.23997, <= 2024.4.1.27687>= 2025.1.0.27937, <= 2025.3.0.35737>= 2026.1.0.36452, <= 2026.1.1.36485<= 2026.1.1.36485CVSS 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
- Low
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Detect Foxit PDF Editor installationCheck for Foxit PDF Editor in typical installation locations: Windows: C:\Program Files\Foxit Software\Foxit PDF Editor\ or C:\Program Files (x86)\Foxit Software\Foxit PDF Editor\. Also check Add/Remove Programs or winget list for 'Foxit PDF Editor'.Affected if Foxit PDF Editor is found on the system
-
Detect Foxit PDF Reader installationCheck for Foxit PDF Reader in typical installation locations: C:\Program Files\Foxit Software\Foxit Reader\ or C:\Program Files (x86)\Foxit Software\Foxit Reader\. Also check Add/Remove Programs or winget list for 'Foxit Reader'.Affected if Foxit PDF Reader is found on the system
-
Retrieve Foxit PDF Editor versionIn the Foxit PDF Editor application, go to Help > About Foxit PDF Editor. Alternatively, right-click the executable file in the installation folder, select Properties, and check the Details tab for the version number.Affected if The installed version falls within any of these ranges: <= 13.2.4.24048; >= 14.0.0.33046 and <= 14.0.4.33508; >= 2023.1.0.15510 and <= 2023.3.0.23028; >= 2024.1.0.23997 and <= 2024.4.1.27687; >= 2025.1.0.27937 and <= 2025.3.0.35737; >= 2026.1.0.36452 and <= 2026.1.1.36485
-
Retrieve Foxit PDF Reader versionIn the Foxit PDF Reader application, go to Help > About Foxit PDF Reader. Alternatively, right-click the executable file in the installation folder, select Properties, and check the Details tab for the version number.Affected if The installed version is <= 2026.1.1.36485
The environment is affected if Foxit PDF Editor or Foxit PDF Reader is installed and its version number matches any of the vulnerable version ranges listed in the CVE.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper synchronization and locking mechanisms to prevent JavaScript reentrancy during page/form operations. Add document state validation checks before memory access to ensure the document status is consistent.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57243 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57243 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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