{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55150 exists.","fix":"No fix has been published for CVE-2025-55150 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-55150 is a high-severity server-side request forgery vulnerability in Stirling-Tools Stirling-PDF, published on 11 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-55150 and fix it if it is affected.\n\nWhat it is: CVE-2025-55150 is a high-severity server-side request forgery vulnerability in Stirling-Tools Stirling-PDF, published on 11 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55150 exists.\n\nAffected product: Stirling-Tools Stirling-PDF. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-55150/ (Markdown: https://insights.sbomify.com/CVE-2025-55150/index.md)","id":"CVE-2025-55150","markdown":"https://insights.sbomify.com/CVE-2025-55150/index.md","name":"CVE-2025-55150","record":{"aliases":["GHSA-xw8v-9mfm-g2pm"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Stirling-PDF web app","requires_auth":"none","summary":"Attackers can bypass sanitization in the HTML-to-PDF conversion endpoint to perform Server-Side Request Forgery, potentially accessing internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"stirling_pdf","vendor":"stirlingpdf"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Stirling-PDF is a locally hosted web application that performs various operations on PDF files. Prior to version 1.1.0, when using the /api/v1/convert/html/pdf endpoint to convert HTML to PDF, the backend calls a third-party tool to process it and includes a sanitizer for security sanitization which can be bypassed and result in SSRF. This issue has been patched in version 1.1.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2025/CVE-2025-55150.yaml","stars":null,"title":"Stirling-PDF \u003c 1.1.0 - Server-Side Request Forgery"}],"tier":"weaponised"},"has_fix":false,"headline":"Stirling-PDF SSRF vulnerability on /api/v1/convert/html/pdf","id":"CVE-2025-55150","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Stirling-PDF SSRF vulnerability on /api/v1/convert/file/pdf","id":"CVE-2025-55151"},"packages":[],"prev":{"headline":"Path Traversal Vulnerability in PDF Review Function (CWE-22)","id":"CVE-2025-55149"},"products":["Stirling-PDF"],"published":"2025-08-11","related":[{"cvss_score":8.6,"headline":"Stirling-PDF SSRF vulnerability on /api/v1/convert/file/pdf","id":"CVE-2025-55151","kev_date_added":null,"published":"2025-08-11"},{"cvss_score":8.6,"headline":"Stirling-PDF SSRF vulnerability on /api/v1/convert/markdown/pdf","id":"CVE-2025-55161","kev_date_added":null,"published":"2025-08-11"},{"cvss_score":7.7,"headline":"Stirling-PDF Server-Side Request Forgery (SSRF)-Induced Arbitrary File Read Vulnerability","id":"CVE-2025-46568","kev_date_added":null,"published":"2025-05-01"},{"cvss_score":3.1,"headline":"Stirling-PDF: Reflected XSS through crafted filename in file upload functionality","id":"CVE-2026-33436","kev_date_added":null,"published":"2026-04-17"},{"cvss_score":2.3,"headline":"Stirling-Tools Stirling-PDF Markdown-to-PDF cross site scripting","id":"CVE-2024-9075","kev_date_added":null,"published":"2024-09-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-12","vendors":["Stirling-Tools"]},"summary":"Attackers can bypass sanitization in the HTML-to-PDF conversion endpoint to perform Server-Side Request Forgery, potentially accessing internal resources.","url":"https://insights.sbomify.com/CVE-2025-55150/"}