CVE-2026-71270

Stirling-PDF Server-Side Request Forgery via /api/v1/convert/url/pdf WeasyPrint Subprocess

Published Aug 5, 2026 CVSS 3.1 · 8.6 High EPSS < 1% KEV · Not listed
Description
Stirling-PDF's POST /api/v1/convert/url/pdf endpoint (ConvertWebsiteToPDF.java) was not updated with the CustomHtmlSanitizer/SsrfProtectionService SSRF protections that were added to three sibling conversion endpoints (html/pdf, file/pdf, markdown/pdf).

Analysis

AI-generated

Technical impact

The POST /api/v1/convert/url/pdf endpoint in Stirling‑PDF lacks the SSRF protections applied to other conversion routes. It validates only that the requested URL resolves to a public IP, then fetches the page’s HTML and hands the unsanitized content to a WeasyPrint subprocess. Embedded resources such as <img src="http://169.254.169.254/..."> are fetched by WeasyPrint without per‑resource filtering, allowing an attacker‑controlled page to cause the server to retrieve internal or cloud metadata endpoints and embed those contents in the generated PDF. The flaw is a Server‑Side Request Forgery (CWE‑918) that can lead to confidential data disclosure.

Affected Systems

The affected product is Stirling‑Tools’ Stirling‑PDF. No specific version range is provided by the CNA, so all publicly available releases that implement the /api/v1/convert/url/pdf endpoint are potentially vulnerable until a fix is released.

Risk and Exploitability

This vulnerability has a CVSS score of 8.6, indicating high severity. The EPSS score is 0.00313, reflecting a very low probability of exploitation, and the vulnerability is not listed in the CISA KEV catalog. Based on the description, it is inferred that the /api/v1/convert/url/pdf endpoint accepts POST requests but the authentication requirements are not documented; an attacker could therefore submit a crafted URL to force the server to retrieve arbitrary resources. Successful exploitation can expose internal network addresses, cloud metadata, and other sensitive data through the PDF output, presenting a significant risk to confidentiality and potentially enabling further attacks.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest official update from Stirling‑Tools that adds SSRF protection to the /api/v1/convert/url/pdf endpoint.
  • If an update is not yet available, restrict inbound traffic to that endpoint using firewall or network ACLs so only trusted IP addresses can send conversion requests.
  • Configure the WeasyPrint subprocess or the host environment to block access to private and cloud‑metadata IP ranges, thereby preventing internal resource retrieval even if the SSRF defense is bypassed.

Generated by OpenCVE AI on August 10, 2026 at 21:04 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description Stirling-PDF's POST /api/v1/convert/url/pdf endpoint (ConvertWebsiteToPDF.java) was not updated with the CustomHtmlSanitizer/SsrfProtectionService SSRF protections that were added to three sibling conversion endpoints (html/pdf, file/pdf, markdown/pdf). The endpoint validates only that the initial requested URL resolves to a public IP, then fetches the page's HTML server-side and hands it, unsanitized, to a WeasyPrint subprocess. Embedded resource references in the fetched HTML (e.g. `<img src="http://169.254.169.254/...">`) are fetched by WeasyPrint with no per-resource SSRF filtering, allowing an attacker-controlled page to cause the server to retrieve cloud metadata endpoints or internal network resources and leak their contents back into the generated PDF. Stirling-PDF's POST /api/v1/convert/url/pdf endpoint (ConvertWebsiteToPDF.java) was not updated with the CustomHtmlSanitizer/SsrfProtectionService SSRF protections that were added to three sibling conversion endpoints (html/pdf, file/pdf, markdown/pdf).
Title Stirling-PDF - Server-Side Request Forgery via /api/v1/convert/url/pdf WeasyPrint Subprocess Stirling-PDF Server-Side Request Forgery via /api/v1/convert/url/pdf WeasyPrint Subprocess
Type Values Removed Values Added
Title Stirling-PDF Server-Side Request Forgery via /api/v1/convert/url/pdf WeasyPrint Subprocess Stirling-PDF - Server-Side Request Forgery via /api/v1/convert/url/pdf WeasyPrint Subprocess
Type Values Removed Values Added
First Time appeared Stirling
Stirling stirling Pdf
Vendors & Products Stirling
Stirling stirling Pdf
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Stirling-PDF's POST /api/v1/convert/url/pdf endpoint (ConvertWebsiteToPDF.java) was not updated with the CustomHtmlSanitizer/SsrfProtectionService SSRF protections that were added to three sibling conversion endpoints (html/pdf, file/pdf, markdown/pdf). The endpoint validates only that the initial requested URL resolves to a public IP, then fetches the page's HTML server-side and hands it, unsanitized, to a WeasyPrint subprocess. Embedded resource references in the fetched HTML (e.g. `<img src="http://169.254.169.254/...">`) are fetched by WeasyPrint with no per-resource SSRF filtering, allowing an attacker-controlled page to cause the server to retrieve cloud metadata endpoints or internal network resources and leak their contents back into the generated PDF.
Title Stirling-PDF Server-Side Request Forgery via /api/v1/convert/url/pdf WeasyPrint Subprocess
Weaknesses CWE-918
References
Metrics cvssV3_1

{'score': 8.6, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N'}

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)

Sources

Status
PUBLISHED
Assigner
TuranSec
Published
Updated
Aug 10, 2026, 11:46 AM
Reserved
Aug 5, 2026, 12:23 PM
Status
Deferred
Published
Aug 5, 2026, 1:24 PM
Modified
Oct 24, 2026, 3:10 PM