dbcve.org
FpdfApplication

CVE-2025-65875

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 arbitrary file upload vulnerability in the AddFont() function of FPDF v1.86 and earlier allows attackers to execute arbitrary code via uploading a crafted PHP 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

Arbitrary file upload vulnerability in FPDF library's AddFont() function allows attackers to upload malicious PHP files and achieve remote code execution. The function lacks proper file type validation, permitting any file type to be stored in accessible web directories.

MitigationUpgrade to patched FPDF version if available; otherwise implement strict file type validation (extension, MIME type, magic bytes) in AddFont() to reject non-font file uploads and disable PHP execution in upload directories.

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
FpdfApplication
Affected:= 1.8.6

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 FPDF library version
    Check composer.json, vendor/fpdf/fpdf/FPDF.php, or any version file for the installed FPDF version number
    Affected if version is exactly 1.8.6 (this is the only affected version)
  2. Locate AddFont() usage in code
    Search application source code for calls to AddFont() method - check controller files, API endpoints, and any user-input handling logic that invokes this function
    Affected if AddFont() is callable from web-facing code without authentication or access controls
  3. Determine upload directory location
    Find where AddFont() stores uploaded font files by reviewing the code - check for $fontfile or similar parameter handling, then verify the full directory path
    Affected if uploaded files are stored in a directory accessible via HTTP (within web root)
  4. Verify PHP execution is permitted in upload directory
    Check server configuration (Apache .htaccess, nginx config) for the upload directory - look for missing 'php_flag engine off' or 'Options -ExecCGI' directives
    Affected if PHP files uploaded via AddFont() can be executed from the storage directory
  5. Inspect file type validation in AddFont()
    Review the AddFont() function implementation in FPDF source - look for missing checks on file extension, MIME type, or file content (magic bytes) before file save operations
    Affected if no validation exists to reject non-font file types (such as .php files)

Environment is affected if FPDF version 1.8.6 is installed AND AddFont() can be invoked over HTTP with uploads stored in a web-accessible directory where PHP execution is allowed.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to patched FPDF version if available; otherwise implement strict file type validation (extension, MIME type, magic bytes) in AddFont() to reject non-font file uploads and disable PHP execution in upload directories.

Recommended fix Moderate confidence

FPDF version newer than 1.8.6 (check official sources for exact fixed release)

  1. 1. Identify all applications and systems that use the FPDF library version 1.8.6 or earlier
  2. 2. Check the official FPDF repository (github.com/Setasign/FPDF) or www.fpdf.org for the latest stable release that addresses this vulnerability
  3. 3. Upgrade FPDF to the fixed version by updating the library dependency in your project (e.g., via Composer: composer update setasign/fpdf or equivalent package manager)
  4. 4. If a fixed version is not yet available, implement file upload validation: restrict AddFont() to accept only expected font file extensions (.ttf, .otf, .pfb, .afm) and validate file MIME types before processing
  5. 5. Ensure the web server runs with minimal privileges and disable PHP execution in upload directories
  6. 6. Test that the AddFont() functionality works correctly after applying the update
  7. 7. Monitor for any security updates or patches from the FPDF maintainers
Caveat Minor: Ensure custom font files conform to the updated validation rules if stricter checks were added

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

Fix this in Fpdf Scoped from the published advisory
  • Consultation1.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,220
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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