Security readout for executives and security teams
Plain-English summary
This CVE describes a high-severity blind SQL injection in LogicalDOC Enterprise through the ComparisonServlet component. An authenticated user could influence database queries, creating risk to document confidentiality, data integrity, and service availability. The provided sources do not name a vendor patch or confirm active exploitation.
Executive priority
Treat this as a near-term remediation priority if LogicalDOC Enterprise is deployed. The risk is high because authenticated compromise could affect sensitive document repositories, but urgency should be balanced against the lack of confirmed active exploitation in the provided evidence.
Technical view
CVE-2025-45868 is CWE-89 SQL injection affecting LogicalDOC Enterprise up to and including v9.1.1. The CVSS 3.1 score is 8.8 with network access, low attack complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Organizations running LogicalDOC Enterprise up to and including v9.1.1 are the likely exposure set. The bundle’s structured affected-product field is incomplete, so version confirmation should come from local asset inventory and vendor guidance.
Exploitation context
The issue requires an authenticated user and is described as blind SQL injection. KEV is false in the bundle, and no provided source states active exploitation in the wild. Public disclosure exists through a GitHub vulnerability write-up reference.
Researcher notes
The source bundle has an inconsistency: narrative fields identify LogicalDOC Enterprise through v9.1.1, while the structured affected list is n/a. Avoid broadening scope beyond LogicalDOC Enterprise until vendor or CVE data is updated. No exploit procedure is needed to validate exposure.
Mitigation direction
- Identify all LogicalDOC Enterprise deployments and exposed interfaces.
- Confirm whether any deployment runs v9.1.1 or earlier.
- Check LogicalDOC vendor guidance for patches or official mitigations.
- Restrict access to LogicalDOC to trusted networks and users where possible.
- Review application and database privilege boundaries for least privilege.
- Increase monitoring for unusual ComparisonServlet and database activity.
Validation and detection
- Verify installed LogicalDOC Enterprise versions against the CVE description.
- Review authentication logs for suspicious low-privilege account activity.
- Inspect application logs for anomalous ComparisonServlet requests.
- Check database logs for unexpected query errors or access patterns.
- Track CVE Program and vendor pages for updated affected-version details.
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-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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 lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration 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-45868 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
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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:H/A:H2.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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-45868/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.