Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privileged account
-
DeliverySend crafted firstLetter to TagsDataServlet
-
ExploitInject UNION SELECT against ld_user
-
ExecutionRead hashes from returned XML tag list
-
ImpactCrack hashes and escalate access
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 an authenticated session with at least a low-privileged LogicalDOC account (PR:L) that can reach TagsDataServlet; the injection point is the firstLetter parameter, which in versions through 9.3 is concatenated directly into a LIKE clause in HibernateDocumentDAO.findTags rather than parameterized. No user interaction and no special non-default configuration is needed beyond normal multi-user operation. The authentication requirement is the primary limiting factor - exploitation is not possible by a fully unauthenticated remote attacker - and impact is limited to data disclosure (read access to ld_user), with no direct write/integrity or availability effect. |
| Impact | This is a credible but bounded risk. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) and CWE-89 are internally consistent with the description: network-reachable, low-complexity, authenticated (PR:L) SQL injection with no user interaction, impacting confidentiality only (VC:H, VI:N/VA:N). The 7.1 score is driven entirely by data disclosure - specifically the ability to dump usernames, emails and password hashes from the ld_user table via UNION SELECT, which creates clear follow-on risk (offline hash cracking, lateral authentication). Mitigating factors lower real-world urgency: exploitation requires a valid low-privileged account (PR:L), a vendor patch exists, and there is no EPSS score, no CISA KEV listing, and no explicitly published exploit in the provided data. The source-code diff from the vendor confirms the root cause (unparameterized string formatting of firstLetter into a LIKE clause, fixed by binding :tagLike), so the vulnerability itself is well-substantiated even though exploitation-probability signals (EPSS) are entirely absent and should be treated as unknown rather than low. Net: a real, patch-now priority for exposed multi-user deployments, but not a mass-exploitation emergency given the authentication requirement and niche product footprint. |
| Exploit ScenarioDerived | A low-privileged authenticated user (or an attacker who has obtained any valid LogicalDOC account) issues a request to TagsDataServlet with a crafted firstLetter value containing a UNION SELECT, causing the injected query to return rows from ld_user inside the XML tag list. The attacker reads usernames, email addresses and password hashes directly from the response, then cracks the hashes offline to escalate to higher-privileged accounts. No public exploit is identified in the provided data, but the vendor commit diff clearly discloses the vulnerable code path. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
SQL injection in LogicalDOC Community Edition through 9.3 allows authenticated low-privileged users to execute crafted SQL via the firstLetter parameter of TagsDataServlet, enabling UNION SELECT statements to be returned in the XML tag list and disclosing usernames, email addresses, and password hashes from the ld_user table. This is a credible but bounded risk: the CVSS 4.0 vector (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) and independent assessment (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) confirm that an authenticated session is required, with no integrity or availability impact; no public exploit identified at time of analysis. The upstream fix commit (8428bfb) parameterizes the vulnerable LIKE clause, but a tagged patched release is not independently confirmed.
RemediationAI
Patch status: Upstream fix available (PR/commit); released patched version not independently confirmed. Apply the upstream commit 8428bfb93f89ab5773019299d17d643c075c4aee, which replaces the string-concatenated LIKE clause in HibernateDocumentDAO.findTags with a parameterized :tagLike placeholder, and upgrade to a LogicalDOC Community Edition release that includes this fix once available (see https://github.com/logicaldoc/community/discussions/119 and the VulnCheck advisory at https://www.vulncheck.com/advisories/logicaldoc-community-edition-through-9.3-sql-injection-via-tags-xml-firstletter). If immediate patching is not possible, compensating controls include restricting access to the TagsDataServlet endpoint (for example, via a reverse proxy or servlet filter that blocks requests to the tags data URL) and removing or disabling unused low-privileged accounts, since exploitation requires an authenticated session; these measures reduce exposure but do not eliminate the injection flaw and may disrupt tag-listing features in the user interface. Additionally, monitor application and database logs for anomalous UNION SELECT patterns in requests to the firstLetter parameter.
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 vulnerability is a CWE-89 SQL injection in LogicalDOC Community Edition, a document management system. In versions through 9.3, the TagsDataServlet exposes a firstLetter parameter that is concatenated directly into a Hibernate SQL query in HibernateDocumentDAO.findTags; the commit diff shows the original code using String.formatted to build a LIKE clause (lower(ld_tag) like '%s%%') before the fix replaced it with a parameterized :tagLike placeholder. Because the query result is serialized into an XML tag list, injected UNION SELECT statements can return arbitrary columns from the backend database-specifically, the advisory notes attackers can read usernames, email addresses, and password hashes from ld_user. The CPE cpe:2.3:a:logicaldoc:logicaldoc_community_edition:*:*:*:*:*:*:*:* confirms all versions are in scope up to the 9.3 code line, and no special non-default configuration is needed beyond normal multi-user operation.
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-reachable servlet, low complexity, but requires a valid low-privileged account so PR:L; impact is confidentiality-only data disclosure from ld_user, hence C:H and I:N/A:N.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
LogicalDOC Community Edition through 9.3 contains a sql injection vulnerability that allows authenticated users to execute crafted SQL via the firstLetter parameter of TagsDataServlet. Low-privileged attackers can inject UNION SELECT statements returned in the XML tag list to read usernames, email addresses and password hashes from ld_user.
Executive ViewAI
LogicalDOC Community Edition deployments through 9.3 are affected by a high-severity SQL injection that allows authenticated low-privileged users to extract usernames, email addresses, and password hashes from the application database. Because this exposes authentication secrets, a single compromised or malicious account could lead to credential theft, lateral movement, and unauthorized access to sensitive document repositories. Leadership should prioritize patching and credential hygiene, especially for externally accessible or business-critical LogicalDOC instances.
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-97448
GHSA-cfx3-f25c-pr5c
NVD
CVE.org
EPSS
Exploit-DB