CVE-2025-45870 LogicalDOC CVE debrief

Who should care

Defenders responsible for LogicalDOC Enterprise deployments should assess their exposure and potential impact. This includes administrators, security teams, and IT personnel managing document management systems.

Why it matters

This LFI vulnerability in LogicalDOC Enterprise could allow authenticated users to access sensitive files outside designated directories, potentially leading to data exposure. Defenders should verify the presence of this vulnerability in their instances, assess the impact, and consider implementing compensating controls.

• Potential unauthorized access to sensitive files.
• Possible data exposure or leakage.
• Need for verification of vulnerable versions in use.
• Potential for lateral movement or escalation of privileges.

Technical summary

The vulnerability exists in the OnlyOfficeEditor servlet class of LogicalDOC Enterprise, allowing an authenticated user to exploit path traversal flaws in the fileExt parameter. This could enable unauthorized access to sensitive files outside designated directories. The vulnerability's technical details indicate that it is a Local File Inclusion (LFI) vulnerability, which can be exploited by an authenticated user. Defenders should prioritize verifying the presence of this vulnerability in their LogicalDOC Enterprise instances and assessing the potential impact on their specific deployment contexts.

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their LogicalDOC Enterprise instances and assessing the potential impact on their specific deployment contexts.

Recommended defensive actions

• Verify the version of LogicalDOC Enterprise in use and assess if it is vulnerable (up to and including 9.1.1).
• Review access controls and authentication mechanisms for the OnlyOfficeEditor servlet class.
• Monitor for potential unauthorized access attempts to sensitive files.
• Consider implementing compensating controls, such as restricting access to sensitive directories.
• Perform a thorough review of system logs to detect any potential exploitation attempts.
• Update documentation to reflect the vulnerability and required mitigations.
• Engage with the vendor for patch guidance and support.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description and CVSS score. However, additional information on exploitation, impact, and remediation is limited. Defenders should verify the presence of this vulnerability in their LogicalDOC Enterprise instances and assess the potential impact on their specific deployment contexts. The lack of detailed information on exploitation and remediation requires defenders to take a cautious approach and implement compensating controls.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.