CVE-2025-55313
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine without logging in, but needs a user to act. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-94 · Code injection
- Record status
- Analyzed
Affected
- Foxit Pdf Editor ≤ 2023.3.0.23028
- Foxit Pdf Editor ≤ 2024.4.1.27687
- Foxit Pdf Editor 2025.1.0.27937
- Foxit Pdf Reader ≤ 2025.1.0.27937
- Foxit Pdf Editor ≤ 13.1.7.63027
- Foxit Pdf Editor ≤ 2023.3.0.63083
- Foxit Pdf Editor ≤ 2024.4.1.66479
- Foxit Pdf Editor 2025.1.0.66692
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-55313.md and follow it. Check whether this project is affected by CVE-2025-55313. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
