Security readout for executives and security teams
Plain-English summary
This flaw could let a logged-in LogicalDOC Enterprise user read sensitive server files that should be outside the application’s document area. It is not described as unauthenticated or actively exploited, but the confidentiality impact is high for affected deployments.
Executive priority
Address in the next vulnerability management cycle, faster for externally reachable systems or environments holding sensitive documents. The issue is not currently supported as actively exploited, but it can expose confidential files to authenticated users.
Technical view
CVE-2025-45870 is a CWE-22 path traversal issue in LogicalDOC Enterprise up to v9.1.1. The OnlyOfficeEditor servlet class mishandles the fileExt parameter, enabling authenticated local file inclusion and unauthorized file reads outside intended directories. CVSS v3.1 is 6.5 medium: network, low complexity, low privileges, no user interaction, high confidentiality impact.
Likely exposure
Exposure is likely limited to organizations running LogicalDOC Enterprise v9.1.1 or earlier. The CVE requires an authenticated user. The provided CVE data does not include CPEs, so defenders should confirm exposure through product and version inventory rather than relying only on automated CPE matching.
Exploitation context
The source bundle does not cite active exploitation, and the CVE is not marked in KEV. Public disclosure includes a GitHub vulnerability write-up, so technical details may be available to researchers and attackers. Treat internet-accessible or broadly user-accessible deployments as higher priority.
Researcher notes
Evidence supports authenticated LFI/path traversal with confidentiality impact only. The affected metadata is sparse: vendor/product fields and CPEs are not populated in the CVE record. Do not assume unauthenticated exploitation, integrity impact, availability impact, or a specific patched version from the supplied sources.
Mitigation direction
- Check LogicalDOC vendor guidance and release notes for an official fix or workaround.
- Prioritize upgrading affected LogicalDOC Enterprise instances when vendor-fixed versions are confirmed.
- Restrict LogicalDOC access to trusted networks and necessary authenticated users.
- Review user permissions and remove unnecessary accounts with access to document editing features.
- Monitor application and web logs for suspicious file-access patterns.
Validation and detection
- Inventory LogicalDOC Enterprise deployments and confirm exact versions.
- Flag v9.1.1 and earlier as potentially affected.
- Confirm whether OnlyOffice editing functionality is enabled and reachable by authenticated users.
- Review logs for unusual requests involving document editor functionality and extension handling.
- Track LogicalDOC advisories for patch confirmation and retest after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-45870 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.logicaldoc.com/CVE reference, mitre
- https://github.com/netero1010/Vulnerability-Disclosure/blob/main/CVE-2025-45870/README.mdCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.