Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with any valid account
-
DeliveryEnumerate/guess restricted folderId
-
ExploitRequest /zip-export?folderId=<restricted>
-
ExecutionServer skips READ/DOWNLOAD checks
-
ImpactReceive ZIP of restricted documents
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation 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 session on the LogicalDOC Community Edition instance (PR:L) - any low-privilege user account is sufficient, no administrative role needed. The attacker must reach the /zip-export servlet over the network and supply a folderId value for a folder they lack READ/DOWNLOAD permission on; folder IDs are sequential numeric identifiers and can be enumerated. No special non-default configuration is required and no user interaction from a victim is needed. The principal limiting factor is that exploitation cannot be performed anonymously - the attacker needs credentials - and the impact is confined to reading document contents (no write or availability effect). Affects versions through 9.3; patched builds restore the permission checks. |
| Impact | This is a genuine but moderate-priority confidentiality issue rather than a critical emergency. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H) confirms network-reachable, low-complexity exploitation but requires authentication (PR:L) - any valid user account suffices, no admin rights needed. Impact is confidentiality-only (VC:H, VI:N/VA:N): an attacker reads documents they should not, but cannot modify or destroy data. No EPSS score, KEV listing, or public POC was provided in the intelligence, so there is no evidence of active or at-scale exploitation; the finding originates from a credible researcher (VulnCheck) and a vendor patch exists. The signals are internally consistent - low real-world urgency driven primarily by the authentication requirement and the limited (read-only) impact - but the lack of EPSS/KEV/POC data means exploitation likelihood cannot be quantified from the input and must be treated as unknown rather than low. |
| Exploit ScenarioDerived | A low-privileged but authenticated LogicalDOC user (e.g. an employee restricted to one department's workspace) sends a request to the /zip-export servlet supplying the folderId of a confidential folder they have no READ or DOWNLOAD rights to. Because ZipExport.addFolderDocuments() omits the permission checks, the server streams back a ZIP archive of every document in that restricted folder. No public exploit code was identified in the provided intelligence, but the attack is a trivial parameter substitution against an authenticated endpoint. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Authenticated users of LogicalDOC Community Edition (versions through 9.3) can bypass folder-level access controls and download the full contents of any restricted folder as a ZIP archive by calling the /zip-export servlet with an arbitrary folderId parameter. Exploitation requires only a valid low-privilege session (CVSS 3.1 PR:L, C:H/I:N/A:N), and because folder IDs are sequential numeric identifiers they can be enumerated, so the practical barrier is low for any user holding an account. The vulnerability is not confirmed as actively exploited (CISA KEV) and no public exploit code was identified at time of analysis, but a vendor fix is available; the impact is limited to confidentiality (document disclosure) with no write or availability effect, making this a moderate-priority information-exposure issue rather than an emergency.
RemediationAI
Apply the vendor-supplied fix: the corrective change is commit 648047ee0ec95c294bb983e511fed60dbc67977f, which reinstates READ/DOWNLOAD permission verification in ZipExport before documents are added to the archive; deploy a build containing this commit rather than running 9.3 or earlier, since vendor advisory data indicates a patch is available but does not state a numbered release. If immediate upgrading is not possible, the most effective compensating control is to restrict access to the /zip-export endpoint at the reverse proxy or web-tier (allow only trusted networks or roles), with the trade-off that legitimate bulk-export functionality is degraded for all users until the patch is applied. Because the flaw only requires an ordinary authenticated account, tightening account provisioning, disabling unused accounts, and monitoring export/download audit events for ZIP retrievals of folders the caller has no READ grant on will reduce exposure, though none of these substitutes for the authorization fix; note that restricting the entire servlet has a broader functional side effect than blocking only non-permitted folder IDs, which is not configurable in the vulnerable code path. Advisory and discussion references: https://github.com/logicaldoc/community/discussions/119, https://github.com/logicaldoc/community, and https://www.vulncheck.com/advisories/logicaldoc-community-edition-through-9.3-missing-authorization-via-zip-export-servlet.
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
LogicalDOC Community Edition is a Java-based document management system. The /zip-export servlet is backed by com.logicaldoc.web.ExportZip, which delegates archive assembly to com.logicaldoc.core.transfer.ZipExport. The flawed path is ZipExport.addFolderDocuments(), which iterates a folder's documents and adds them to a ZipArchiveOutputStream without invoking the FolderDAO permission checks (isDownloadAllowed / READ checks) that the sibling code path for explicit document-ID exports does perform. This is a classic CWE-862 (Missing Authorization) failure: the application authenticates the request but never authorizes the caller against the target folder's ACL. The supplied folderId is a plain numeric identifier assigned sequentially by the repository, which makes it trivially guessable or enumerable by any logged-in user. The upstream commit 648047ee0ec95c294bb983e511fed60dbc67977f restores the permission verification in ZipExport (introducing SessionManager usage and reworking the export logic), confirming the root cause is an absent access-control check rather than an encoding or path-handling defect.
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 (AV:N), trivial parameter change (AC:L), requires any authenticated account (PR:L), no user interaction; read-only document disclosure yields C:H with no integrity or availability impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
LogicalDOC Community Edition through 9.3 contains a missing authorization vulnerability in the zip-export servlet that allows authenticated users to export restricted folders by supplying a folderId parameter. Attackers can request /zip-export with a restricted folder ID, since ZipExport.addFolderDocuments() skips READ and DOWNLOAD permission checks, to download all of its documents in a ZIP archive.
Executive ViewAI
LogicalDOC Community Edition (versions through 9.3) allows any authenticated user holding a basic account to bypass folder-level permissions and export the entire contents of restricted folders as a single ZIP file, putting confidential documents stored in the platform at direct risk of bulk disclosure. Because folder identifiers are predictable sequential numbers, a low-privilege user - or anyone who compromises such an account - can systematically harvest restricted content, meaning the organizations affected are those using this document management platform to hold contracts, HR records, or regulated data. A vendor fix is available and there is no evidence of active exploitation today, so this is a contained, remediation-driven exposure rather than an active breach.
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
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-97443
GHSA-q2v3-rpjf-5cc3
NVD
CVE.org
EPSS
Exploit-DB