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

> Unauthenticated attackers can trigger server-side requests to arbitrary hosts via the ShareFileCallback servlet in LogicalDOC Enterprise.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** GHSA-p38p-xrw4-9mj3

## What is CVE-2025-45869?

CVE-2025-45869 is a high-severity server-side request forgery vulnerability in n/a, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LogicalDOC Enterprise Version up to and before v9.1.1 is vulnerable to Server-Side Request Forgery (SSRF). An unauthenticated attacker can exploit the ShareFileCallback servlet by manipulating input parameters to trigger a server-side request to an attacker-controlled host.

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

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


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

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

## Is CVE-2025-45869 being exploited?

There is no known exploitation of CVE-2025-45869 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-45869 is a high-severity server-side request forgery vulnerability in n/a, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-45869 in the wild and no public exploit code.

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-45869/ (Markdown: https://insights.sbomify.com/CVE-2025-45869/index.md)
```

## Sources

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

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