dbcve.org
ErpnextApplication · Frappe

CVE-2026-31017

CRITICAL · 9.1 CVSS v3.1 Published 2026-04-08
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
A Server-Side Request Forgery (SSRF) vulnerability exists in the Print Format functionality of ERPNext v16.0.1 and Frappe Framework v16.1.1, where user-supplied HTML is insufficiently sanitized before being rendered into PDF. When generating PDFs from user-controlled HTML content, the application allows the inclusion of HTML elements such as <iframe> that reference external resources. The PDF rendering engine automatically fetches these resources on the server side. An attacker can abuse this behavior to force the server to make arbitrary HTTP requests to internal services, including cloud metadata endpoints, potentially leading to sensitive information disclosure.

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

This is an SSRF vulnerability in ERPNext v16.0.1 and Frappe Framework v16.1.1 where the Print Format PDF generation functionality fails to sanitize user-supplied HTML. Malicious HTML containing elements like <iframe> tags are processed by the PDF rendering engine on the server side, causing the server to automatically fetch external resources. An attacker can exploit this to make the server request internal services, cloud metadata endpoints (e.g., AWS169.254.169.254), and retrieve sensitive data.

MitigationImplement strict HTML sanitization in the Print Format PDF generation pipeline to strip or block external resource-loading elements (iframe, img with external src, object, embed, link, etc.) before PDF rendering. Alternatively, enforce network segmentation to prevent PDF generation workers from accessing internal/metadata endpoints.

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
ErpnextApplication
Affected:= 16.0.1
FrappeApplication
Affected:= 16.1.1

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
None

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

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. Check installed Frappe Framework version
    Run 'bench version' or check the version file in your Frappe installation directory (usually in the site_config.json or via Frappe's About page in the system).
    Affected if The installed Frappe version is exactly 16.1.1
  2. Check installed ERPNext version
    Run 'bench version' or access ERPNext About page (/app/about) to view the installed version.
    Affected if The installed ERPNext version is exactly 16.0.1
  3. Verify Print Format feature is accessible
    Log into the ERPNext/Frappe system as a user with permissions and navigate to Settings > Print Format Designer or access an existing Print Format (e.g., /app/print-format).
    Affected if Print Format Designer or custom print formats can be accessed and edited by users
  4. Confirm custom HTML can be inserted in Print Formats
    Open a Print Format in edit mode and verify that HTML can be added via the Custom HTML field or Print Format Builder.
    Affected if Users can add custom HTML content including iframe, object, embed, form, or CSS @import elements to print formats
  5. Verify PDF rendering is enabled and accessible
    Attempt to generate a PDF from any document that uses an affected print format to confirm the rendering pipeline is active.
    Affected if PDF rendering from print formats is functional and can be triggered

You are affected if you are running exactly Frappe Framework v16.1.1 or ERPNext v16.0.1 AND your users have access to create or edit Print Formats with custom HTML that can trigger external resource loading during PDF rendering.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict HTML sanitization in the Print Format PDF generation pipeline to strip or block external resource-loading elements (iframe, img with external src, object, embed, link, etc.) before PDF rendering. Alternatively, enforce network segmentation to prevent PDF generation workers from accessing internal/metadata endpoints.

Fix this in Erpnext Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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