Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privilege account
-
DeliveryObtain read access to any folder
-
ExploitInject boolean HQL via 'indexed' parameter
-
ExecutionBypass folder scope and permission checks
-
ImpactExtract restricted document metadata and database contents
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a valid authenticated LogicalDOC Community Edition account (through v9.3) holding read permission on at least one folder (PR:L). The attacker then supplies a malicious 'indexed' request parameter to DocumentsDataServlet (the documents.xml data endpoint), which is concatenated unvalidated into the HQL query (query.append(" and A.indexingStatus = %s")). No non-default configuration or special feature toggle is needed - the vulnerable servlet is part of the standard web application. The primary limiting factor is the authentication requirement (any read-access user suffices); there is no user-interaction requirement, and impact is restricted to confidentiality (metadata/database read), not modification or denial of service. |
| Impact | Signals are moderately consistent and point to a real but bounded data-confidentiality issue rather than a critical priority. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) indicates a network-reachable, low-complexity attack requiring only low privileges and no user interaction, with impact confined to confidentiality (VC:H, VI:N, VA:N) - consistent with the description, which limits the flaw to reading restricted document metadata and database contents via HQL injection (CWE-89). The score of 7.1 (High) is driven entirely by the confidentiality impact; there is no integrity or availability impact and no scope change, so this is not a remote-code-execution or takeover scenario. No EPSS probability was provided, the CVE is NOT in CISA KEV, and no POC was supplied, so exploitation status is: no public exploit identified at time of analysis. The key limiting factor is PR:L - an attacker must already hold a valid authenticated account with read access to at least one folder, which lowers real-world exploitability compared to an unauthenticated flaw. Mitigating this, a vendor patch is confirmed available (parameterizing the query), and the fix commit publicly reveals the exact vulnerable code path, which could accelerate exploit development. Net: a genuine authenticated information-disclosure bug worth patching, but lower urgency than an unauthenticated or RCE-class issue. |
| Exploit ScenarioDerived | A low-privileged but authenticated LogicalDOC user who has read access to any single folder sends a request to DocumentsDataServlet with a crafted 'indexed' parameter containing a boolean HQL expression. Because the parameter is concatenated directly into the HQL query, the attacker bypasses folder-scope and read-permission checks and enumerates metadata of documents they should not see, ultimately extracting broader database contents. No public exploit code is identified, but the vendor fix commit discloses the exact vulnerable line, lowering the barrier to weaponization. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
An HQL injection in LogicalDOC Community Edition through 9.3 lets any authenticated user who holds read permission on a single folder escape that folder's scope and read document metadata and database contents they are not entitled to see. The flaw is reachable through the documents.xml data endpoint (DocumentsDataServlet), where the 'indexed' request parameter is concatenated unvalidated into a Hibernate query, so the primary barrier is only the requirement for a low-privileged, read-only account; impact is limited to confidentiality with no modification or denial of service. There is no vendor patch version confirmed in the available data beyond the upstream fix commit, and no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, though an advisory and public discussion exist.
RemediationAI
Apply the upstream fix, which is available in the LogicalDOC community repository commit c3bbfd4641f1cd2b340f114ea198d3f65b6581ee; that change replaces the string-concatenated HQL fragment with a Hibernate named parameter (:indexingStatus) so the 'indexed' value is bound, not interpreted, and it is the authoritative code-level remediation for this vulnerability - confirm the corresponding patched release or build with the vendor via the advisory at https://www.vulncheck.com/advisories/logicaldoc-community-edition-through-9.3-hql-injection-via-documents-xml-indexed-parameter and the project discussion at https://github.com/logicaldoc/community/discussions/119, since an exact fixed version number is not independently confirmed in the available data. If upgrading must be delayed, compensating controls include restricting access to the affected data servlet mapping (the documents.xml data endpoint) to trusted or administrative users via a servlet filter or reverse-proxy ACL - the trade-off being that ordinary read-only users lose the document listing functionality served by that endpoint - and deploying a WAF rule that rejects or normalizes 'indexed' parameter values containing HQL metacharacters, quotes, comparison operators, or boolean keywords such as 'or', 'and', and subquery syntax, with the trade-off of possible false positives on legitimate indexing-status values. Because exploitation requires only a low-privileged authenticated account with read access to one folder, also review LogicalDOC accounts and their folder permissions to minimize the number of users who can reach the endpoint, and audit web/application logs for anomalous 'indexed' parameter values hitting the documents data servlet as a detection measure.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected code is the Java servlet com.logicaldoc.web.data.DocumentsDataServlet in the logicaldoc-webapp module, which is part of the standard LogicalDOC Community Edition web application (CPE cpe:2.3:a:logicaldoc:logicaldoc_community_edition). When handling a request for the documents.xml data endpoint, the servlet builds a Hibernate Query Language (HQL) statement dynamically and, before the fix, appended the caller-supplied 'indexed' parameter directly into the query string with query.append(" and A.indexingStatus = %s".formatted(request.getParameter(INDEXED))). Because HQL, like SQL, is an interpreted query language, an attacker can supply boolean expressions (for example conditions that evaluate to true for all rows, or subselect-style predicates) instead of a simple status value, modifying the query's WHERE clause and neutralizing the folder-scope and read-permission predicates the application relies on to restrict results. This is a classic CWE-89 (SQL/query injection) root cause: untrusted input reaching a query interpreter without parameter binding. The upstream fix changes the vulnerable line to use a named parameter (query.append(" and A.indexingStatus = :indexingStatus") with params.put("indexingStatus", ...)), letting Hibernate bind the value safely rather than composing the query text.
Know when Logicaldoc gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Network-facing servlet with low-complexity injection, but a read-access authenticated account is required so PR:L; impact is confidentiality-only (database/metadata disclosure), so I:N and A:N.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
LogicalDOC Community Edition through 9.3 contains an HQL injection vulnerability in DocumentsDataServlet that allows authenticated users to manipulate queries via the unvalidated indexed parameter. Attackers with read access to any folder can inject boolean HQL expressions to bypass folder scope and read-permission checks, listing restricted document metadata and extracting database contents.
Executive ViewAI
LogicalDOC Community Edition through version 9.3 contains a query-injection flaw that allows a user with read access to a single folder to view document metadata and database records belonging to folders they were never granted permission to see. Because the product is commonly used as a repository for contracts, HR records, and other regulated content, any organization running an affected release should assume its folder-level segregation controls may not be trustworthy. The exposure is confidentiality-only and requires a valid low-privilege account, but it effectively defeats the permission model leadership relies on to keep sensitive documents compartmentalized.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
More in Logicaldoc
View allLogicalDoc before 8.3.3 could allow an attacker to upload arbitrary files, leading to command execution or retrieval of
LogicalDoc Community Edition 7.5.3 and prior is vulnerable to XXE when indexing XML documents. Rated high severity (CVSS
LogicalDoc Community Edition 7.5.3 and prior contain an Incorrect access control which could leave to privilege escalati
A local privilege elevation vulnerability exists in the file system permissions of LogicalDoc 8.5.1 installation. Rated
LogicalDoc before 8.3.3 allows /servlet.gupld Directory Traversal, a different vulnerability than CVE-2020-9423 and CVE-
LogicalDOC Community Edition 8.x before 8.2.1 has a path traversal vulnerability that allows reading arbitrary files and
LogicalDoc before 8.3.3 allows SQL Injection. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitab
LogicalDoc Community Edition 7.5.3 and prior is vulnerable to an XSS when using preview on HTML document. Rated medium s
The API used to interact with documents in the application contains two endpoints with a flaw that allows an authenticat
Unauthenticated multipart uploads to the LogicalDOC Community Edition /upload endpoint (through version 9.3) let remote
Authenticated remote code execution in LogicalDOC Community Edition through 9.3 allows any user with a valid account to
Missing authorization in LogicalDOC Community Edition through 9.3 allows any authenticated low-privilege user to disclos
EUVD-2026-97447
GHSA-q5m2-qppc-8h4c
NVD
CVE.org
EPSS
Exploit-DB