dbcve.org
Stirling PdfApplication · Stirlingpdf

CVE-2025-55151

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-11
Fix available
A fix is available. Upgrade to 1.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Stirling-PDF is a locally hosted web application that performs various operations on PDF files. Prior to version 1.1.0, the "convert file to pdf" functionality (/api/v1/convert/file/pdf) uses LibreOffice's unoconvert tool for conversion, and SSRF vulnerabilities exist during the conversion process. This issue has been patched in version 1.1.0.

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

Stirling-PDF's convert file to PDF functionality at /api/v1/convert/file/pdf uses LibreOffice's unoconvert tool, which contains SSRF vulnerabilities allowing attackers to make the server request arbitrary internal or external resources during the conversion process.

MitigationUpgrade Stirling-PDF to version 1.1.0 or later to patch the SSRF vulnerability in the LibreOffice unoconvert integration.

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
Stirling PdfApplication
Affected:< 1.1.0

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 installed Stirling-PDF version
    Check the version via Docker container labels, application startup logs, or the UI footer. Common endpoints include /api/v1/info or the main page source. Compare against the affected range: versions prior to 1.1.0 are vulnerable.
    Affected if Running version 1.1.0 or later means not affected; versions below 1.1.0 are in the affected range.
  2. Confirm the vulnerable endpoint is exposed
    Verify the application serves the /api/v1/convert/file/pdf route. This is typically accessible on the same port as the main web interface (usually 8080). Check if the endpoint responds to OPTIONS or GET requests.
    Affected if If the endpoint returns a valid HTTP response (even an error), it is exposed and potentially exploitable if version is below 1.1.0.
  3. Verify LibreOffice conversion functionality is enabled
    Check if LibreOffice is installed and available to the container/process. Look for unoconvert or soffice binaries in the runtime environment. In Docker deployments, verify the image includes LibreOffice dependencies.
    Affected if If LibreOffice is installed and the conversion features are functional, the SSRF attack surface exists.

A user is affected if their Stirling-PDF version is below 1.1.0, the /api/v1/convert/file/pdf endpoint is accessible, and LibreOffice conversion is enabled.

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
Upgrade available Upgrade to 1.1.0 or later
Fixed in 1.1.0
Vendor patch github.com →
Interim mitigation

Upgrade Stirling-PDF to version 1.1.0 or later to patch the SSRF vulnerability in the LibreOffice unoconvert integration.

Recommended fix High confidence

1.1.0

  1. Back up the current Stirling-PDF installation and any existing data
  2. Stop the running Stirling-PDF service
  3. Download version 1.1.0 from the official GitHub releases at https://github.com/Stirling-Tools/Stirling-PDF/releases
  4. Replace the existing Stirling-PDF installation files with the new version 1.1.0
  5. Restart the Stirling-PDF service
  6. Verify the application is running and test the convert file to pdf functionality (/api/v1/convert/file/pdf)
Caveat none documented in the release notes

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

Fix this in Stirling Pdf Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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