Quick answers
- Is CVE-2025-45871 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-45871 being exploited in the wild.
- How severe is CVE-2025-45871?
- Informational severity, published 6 October 2026.
- Which products and versions are affected?
- LogicalDOC Enterprise up to and including 9.1.1.
- Is there a fix for CVE-2025-45871?
- Yes: fixed in LogicalDOC 9.2. Until then: Validate and sanitize all workflow template names and query parameters; use parameterized SQL queries with proper statement binding instead of string concatenation to prevent SQL injection attacks. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-45871 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2025-45871?
- Check whether you run LogicalDOC Enterprise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: LogicalDOC 9.2
Validate and sanitize all workflow template names and query parameters; use parameterized SQL queries with proper statement binding instead of string concatenation to prevent SQL injection attacks.
Technical details
Blind SQL injection in the WorkflowsDataServlet component, specifically the printDeployed function, which constructs a SQL query using the workflow template name without proper sanitization or parameterized queries. An authenticated attacker creates a malicious workflow template name that is later used directly in a SQL query; the boolean response (deployed/not deployed) serves as a side channel to extract database contents. A fix is indicated for version 9.2.
Affected products
- LogicalDOC Enterprise up to and including 9.1.1
Timeline
- 2026-10-06: disclosed
- 2026-10-06: advisory