VulnerabilityPublished 3 Feb 2026Updated 4 Feb 2026

CVE-2025-65875: fpdf · CVE-2025-65875 is a high-severity arbitrary file upload

Affects fpdfSource CVE Database V5

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

8.8High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:L/S:U/UI:N

Attack Complexity: Low
Attack Vector: Network
Availability: High
Confidentiality: High
Integrity: High
Privileges Required: Low
Scope: Unchanged
User Interaction: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Packagistsetasign/fpdf`pkg:composer/setasign/fpdf`Other threats	Affected <=1.86	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Since no official patches are currently available, European organizations should implement the following specific mitigations: 1) Immediately audit all web applications using FPDF to identify vulnerable versions (v1.86 and earlier). 2) Restrict file upload permissions and disable font uploads where not strictly necessary. 3) Implement strict server-side validation to verify the file type and reject any non-font or executable files. 4) Use web application firewalls (WAFs) to detect and block attempts to upload PHP or other executable files disguised as fonts. 5) Monitor web server logs and file upload directories for suspicious activity or unexpected file types. 6) Consider isolating PDF generation services in segmented environments with minimal privileges to limit potential damage. 7) Prepare to update or patch FPDF immediately once a fix is released. 8) Educate developers about secure file handling practices to prevent similar vulnerabilities. These steps go beyond generic advice by focusing on the specific attack vector and the nature of the vulnerable function.

Description

CVE-2025-65875 is a high-severity arbitrary file upload vulnerability in the AddFont() function of FPDF version 1.86 and earlier. It allows attackers with low privileges to upload crafted PHP files without user interaction, leading to remote code execution. The vulnerability impacts confidentiality, integrity, and availability of affected systems and can be exploited remotely over the network. No known exploits are currently in the wild, and no patches have been published yet. European organizations using vulnerable FPDF versions in web applications are at risk, especially those in sectors relying heavily on PDF generation. Mitigation involves restricting file upload capabilities, implementing strict input validation, and monitoring for suspicious file uploads. Countries with significant software development and digital services sectors, such as Germany, France, and the UK, are more likely to be affected. Due to the high impact and ease of exploitation, this vulnerability demands urgent attention from defenders.

Impact

For European organizations, the impact of CVE-2025-65875 can be severe. Organizations using FPDF in web applications—especially those generating PDFs dynamically—may face remote code execution attacks, leading to full system compromise. This can result in data breaches, unauthorized access to sensitive information, disruption of services, and potential lateral movement within networks. Sectors such as finance, government, healthcare, and digital services that rely on PDF generation are particularly vulnerable. The vulnerability's exploitation could undermine trust in digital services and lead to regulatory penalties under GDPR if personal data is compromised. Additionally, the ability to execute arbitrary code remotely without user interaction increases the risk of automated exploitation campaigns targeting vulnerable European infrastructure. The lack of patches and the ease of exploitation heighten the urgency for European organizations to assess their exposure and implement mitigations promptly.

Summary

CVE-2025-65875 is an arbitrary file upload vulnerability identified in the AddFont() function of the FPDF library version 1.86 and earlier. FPDF is a widely used PHP library for generating PDF documents dynamically. The vulnerability arises because the AddFont() function improperly handles font file uploads, allowing an attacker to upload a maliciously crafted PHP file disguised as a font file. Since the uploaded file can be executed on the server, this leads to remote code execution (RCE) without requiring user interaction. The CVSS v3.1 score of 8.8 reflects the high severity, with an attack vector over the network (AV:N), low attack complexity (AC:L), no user interaction (UI:N), and requiring only low privileges (PR:L). The vulnerability affects confidentiality, integrity, and availability by enabling arbitrary code execution, potentially allowing attackers to take full control of the affected server. Although no known exploits are currently reported in the wild, the lack of patches and the critical nature of the vulnerability make it a significant threat. The vulnerability is classified under CWE-434 (Unrestricted Upload of File with Dangerous Type), indicating improper validation of uploaded files. Since FPDF is commonly integrated into web applications for PDF generation, any web-facing application using vulnerable versions is at risk. The absence of official patches necessitates immediate mitigation through configuration changes and monitoring.

CWE-434Unrestricted Upload of File with Dangerous Type (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #12OWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
Architecture and Design
Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Architecture and Design
Consider storing the uploaded files outside of the web document root entirely. Then, use other mechanisms to deliver the files dynamically.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Web Service Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
File Upload (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V12.5.2 (opens in a new tab)
V13.1.5 (opens in a new tab)
V12.2.1 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Feb 2026, 12:04 UTC

WeaknessesCWE-434

Technical details

References

Community reviews

Related threats