dbcve.org
Pdf EditorApplication · Foxit

CVE-2025-55313

HIGH · 7.8 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to after 2025.1.0.66692 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
An issue was discovered in Foxit PDF and Editor for Windows and macOS before 13.2 and 2025 before 2025.2. They allow potential arbitrary code execution when processing crafted PDF files. The vulnerability stems from insufficient handling of memory allocation failures after assigning an extremely large value to a form field's charLimit property via JavaScript. This can result in memory corruption and may allow an attacker to execute arbitrary code by persuading a user to open a malicious file.

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

Foxit PDF Editor contains a memory corruption vulnerability where assigning an extremely large value to a form field's charLimit property via JavaScript causes improper handling of memory allocation failures, leading to memory corruption that can be leveraged for arbitrary code execution.

MitigationUpdate Foxit PDF Editor to version 13.2 or 2025.2 or later. Until patched, avoid opening untrusted PDF files and consider disabling JavaScript execution in the application if acceptable for your use case.

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

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 installed Foxit product and version
    Open Foxit PDF Editor or Reader, then go to Help > About Foxit PDF Editor/Reader to view the exact version number. Alternatively, right-click the application in the Start menu and select Properties to view the version.
    Affected if The installed version falls within any of these ranges: >= 2023.1.0.15510 and <= 2023.3.0.23028; >= 2024.1.0.23997 and <= 2024.4.1.27687; = 2025.1.0.27937; <= 13.1.7.63027; >= 2023.1.0.55583 and <= 2023.3.0.63083; >= 2024.1.0.63682 and <= 2024.4.1.66479; = 2025.1.0.66692 for Editor; or <= 2025.1.0.2
  2. Verify JavaScript execution is enabled in Foxit
    In Foxit PDF Editor/Reader, go to File > Preferences > JavaScript. Confirm whether the option 'Enable Adobe JavaScript' is checked.
    Affected if JavaScript execution is enabled, as the vulnerability is triggered by assigning a large value to a form field's charLimit property via JavaScript.
  3. Check for PDF forms with JavaScript usage
    Open any PDF forms or documents you work with. In Foxit, go to Form > JavaScript Actions to see if any JavaScript scripts are attached to form fields or document events.
    Affected if The document contains form fields with JavaScript actions, particularly those that manipulate the charLimit property, as this is the specific attack vector for this vulnerability.

You are affected if you are running a Foxit PDF Editor or Reader version within the affected ranges listed above and JavaScript execution is enabled in the application.

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 2025.2 or later. Until patched, avoid opening untrusted PDF files and consider disabling JavaScript execution in the application if acceptable for your use case.

Recommended fix High confidence

Foxit PDF Editor 13.2+ or 2025.2+; Foxit PDF Reader 2025.2+

  1. Identify the currently installed Foxit PDF Editor or Reader version via Help > About
  2. Navigate to the official Foxit website (www.foxit.com) and download the latest version (13.2 or later for versioned releases, or 2025.2 or later for year-based releases)
  3. Uninstall the current vulnerable version of Foxit PDF Editor or Reader
  4. Install the newly downloaded fixed version (13.2+/2025.2+)
  5. Verify the installation by checking Help > About to confirm the version number
Caveat Standard upgrade; review release notes for any feature changes

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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