dbcve.org
Pdf EditorApplication · Foxit

CVE-2025-55309

MEDIUM · 6.7 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to after 2025.1.0.66692 or later.
See remediation →
67/100
Remediation priority · Elevated

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
An issue was discovered in Foxit PDF and Editor for Windows and macOS before 13.2 and 2025 before 2025.2. A crafted PDF can contain JavaScript that attaches an OnBlur action on a form field that destroys an annotation. During user right-click interaction, the program's internal focus change handling prematurely releases the annotation object, resulting in a use-after-free vulnerability that may cause memory corruption or application crashes.

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

A use-after-free vulnerability in Foxit PDF Reader and Editor on Windows and macOS allows a crafted PDF containing malicious JavaScript to trigger premature release of an annotation object during focus change handling when the user performs a right-click interaction. The OnBlur action on a form field destroys the annotation while it's still referenced, leading to memory corruption and potential code execution or application crashes.

MitigationUpdate Foxit PDF Editor to version 13.2 or later (for the 13.x branch) or version 2025.2 or later (for the 2025 branch). Avoid opening untrusted PDF files from unknown sources as a temporary precaution.

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.1.7.63027>= 2023.1.0.55583, <= 2023.3.0.63083>= 2024.1.0.63682, <= 2024.4.1.66479= 2025.1.0.66692<= 13.1.7.23637>= 2023.1.0.15510, <= 2023.3.0.23028>= 2024.1.0.23997, <= 2024.4.1.27687= 2025.1.0.27937
Pdf ReaderApplication
Affected:<= 2025.1.0.66692<= 2025.1.0.27937

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

CVSS:3.1/AV:L/AC:H/PR:L/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 installed Foxit product
    On Windows, check Program Files or Program Files (x86) for 'Foxit PDF Reader' or 'Foxit PDF Editor' folders. On macOS, check /Applications for Foxit apps.
    Affected if Foxit PDF Reader or Foxit PDF Editor is installed
  2. Determine installed version on Windows
    Right-click the Foxit executable (e.g., FoxitPDFReader.exe or FoxitPDFEditor.exe), select Properties, and view the 'Details' tab for the 'Product version' field.
    Affected if Version number matches any of the affected ranges listed in the CVE
  3. Determine installed version on macOS
    Right-click the Foxit app in /Applications, select 'Get Info', and view the 'Version' field under the General section.
    Affected if Version number matches any of the affected ranges listed in the CVE
  4. Compare version against affected ranges
    Match your installed version number against these vulnerable ranges: Foxit PDF Editor <= 13.1.7.63027; >= 2023.1.0.55583 <= 2023.3.0.63083; >= 2024.1.0.63682 <= 2024.4.1.66479; = 2025.1.0.66692; <= 13.1.7.23637; >= 2023.1.0.15510 <= 2023.3.0.23028; >= 2024.1.0.23997 <= 2024.4.1.27687; = 2025.1.0.27937. Foxit PDF Reader <= 2025.1.0.66692 or <= 2025.1.0.27937.
    Affected if Installed version falls within any of the listed vulnerable version ranges

The environment is affected if Foxit PDF Reader or Foxit PDF Editor is installed and its version matches any of the vulnerable version ranges specified in the CVE.

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 a release after 2025.1.0.66692
Interim mitigation

Update Foxit PDF Editor to version 13.2 or later (for the 13.x branch) or version 2025.2 or later (for the 2025 branch). Avoid opening untrusted PDF files from unknown sources as a temporary precaution.

Recommended fix High confidence

Foxit PDF Editor 13.2+ / 2023.4+ / 2024.5+ / 2025.2+; Foxit PDF Reader 2025.2+

  1. 1. Identify the currently installed Foxit PDF Editor or Reader version from the application Help > About menu
  2. 2. For Pdf Editor version 13.x: upgrade to version 13.2 or later
  3. 3. For Pdf Editor 2023.x (versions 2023.1.0.55583 through 2023.3.0.63083): upgrade to version 2023.4 or later
  4. 4. For Pdf Editor 2024.x (versions 2024.1.0.63682 through 2024.4.1.66479): upgrade to version 2024.5 or later
  5. 5. For Pdf Editor 2025.x (version 2025.1.0.66692): upgrade to version 2025.2 or later
  6. 6. For Pdf Reader: upgrade to version 2025.2 or later
  7. 7. After upgrading, verify the new version by checking Help > About in the application

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

Fix this in Pdf Editor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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