dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-45869

HIGH · 7.3 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click 5 weeks old

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
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.

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

LogicalDOC Enterprise up to v9.1.1 contains an unauthenticated SSRF vulnerability in the ShareFileCallback servlet. Attackers can manipulate input parameters to force the server to make requests to attacker-controlled hosts, potentially enabling internal service enumeration, cloud metadata access, or further attacks.

MitigationUpdate to LogicalDOC v9.1.1 or later to receive the vendor patch. If immediate patching is not feasible, consider restricting network access to the ShareFileCallback endpoint via firewall rules or web application firewall (WAF) configurations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 LogicalDOC version
    Locate the LogicalDOC installation directory and check version information in the product's about page, version file, or admin console. Common locations include the admin panel, a version.info file, or the WAR/zip metadata.
    Affected if The installed version is LogicalDOC Enterprise version 9.1.1 or any earlier version (any version up to and including 9.1.1).
  2. Verify ShareFileCallback servlet presence
    Search for the ShareFileCallback servlet in the deployed web application files. Look for servlet mappings in web.xml or equivalent configuration files, or check for the presence of a ShareFileCallback class in the application's class files.
    Affected if The ShareFileCallback servlet exists in the deployment, indicating the vulnerable component is present.
  3. Confirm endpoint accessibility
    Attempt to access the ShareFileCallback endpoint via HTTP/HTTPS (typically at a path containing 'ShareFileCallback' or similar). Check if the endpoint responds without requiring authentication.
    Affected if The ShareFileCallback endpoint is reachable over the network without authentication, meaning an unauthenticated attacker could potentially exploit the SSRF vulnerability.

If the installed LogicalDOC Enterprise version is 9.1.1 or earlier and the unauthenticated ShareFileCallback servlet is accessible, the environment is affected by this SSRF vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to LogicalDOC v9.1.1 or later to receive the vendor patch. If immediate patching is not feasible, consider restricting network access to the ShareFileCallback endpoint via firewall rules or web application firewall (WAF) configurations.

Recommended fix Moderate confidence

LogicalDOC Enterprise v9.1.1 or later (recommended: latest stable v9.x release)

  1. 1. Identify the currently deployed LogicalDOC version by checking the administration console or the product's about page
  2. 2. Download the latest LogicalDOC Enterprise version from the official vendor website at www.logicaldoc.com
  3. 3. Review the release notes for version 9.1.1 or later to confirm the SSRF vulnerability in ShareFileCallback servlet is addressed
  4. 4. Before applying the upgrade in production, test the new version in a staging environment to verify the fix and ensure compatibility with existing configurations
  5. 5. Create a full backup of the current LogicalDOC installation including database and configuration files
  6. 6. Execute the upgrade following the vendor's official upgrade procedure documented in the installation guide
  7. 7. After upgrade, verify the ShareFileCallback servlet is properly configured and input validation is enforced
  8. 8. Confirm the vulnerability is resolved by attempting benign SSRF tests in a test environment (e.g., verify the server no longer makes arbitrary outbound connections to untrusted URLs)
Caveat Review upgrade notes for potential breaking changes between current version and v9.1.1+; some configuration adjustments may be needed

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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