# CVE-2025-55853: Server-side request forgery in n/a

> An attacker can upload malicious files to trigger SSRF and LFI, enabling internal port scanning and local file access in webPDF.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-ww95-r66q-v2hh

## What is CVE-2025-55853?

CVE-2025-55853 is a critical server-side request forgery vulnerability in n/a, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SoftVision webPDF before 10.0.2 is vulnerable to Server-Side Request Forgery (SSRF). The PDF converter function does not check if internal or external resources are requested in the uploaded files and allows for protocols such as http:// and file:///. This allows an attacker to upload an XML or HTML file in the application, which when rendered to a PDF allows for internal port scanning and Local File Inclusion (LFI).

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2025-55853?

It affects 1 product.


Products: Softvision Webpdf.

## How do I fix CVE-2025-55853?

No fix has been published for CVE-2025-55853 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-55853 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55853 exists.

Public exploit code:

- Local File Inclusion via Server Side Request Forgery (github_poc): https://github.com/Vivz13/CVE-2025-55853

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-55853 and fix it if it is affected.

What it is: CVE-2025-55853 is a critical server-side request forgery vulnerability in n/a, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55853 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-55853/ (Markdown: https://insights.sbomify.com/CVE-2025-55853/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-55853
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-55853
- OSV: https://osv.dev/vulnerability/CVE-2025-55853

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-55853/
Summaries are generated and may contain mistakes; the official description above is the record.