Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed kkFileView upload endpoint
-
DeliveryCraft multipart request with traversal path
-
ExploitBypass missing path validation in FileController
-
ExecutionWrite webshell outside fileDir root
-
ImpactRequest planted file for code execution
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network reachability to a kkFileView 5.0.0-5.0.2 instance and that the file-management endpoints (fileUpload, createFolder, existsFile) are exposed; the attacker supplies a 'path' request parameter that is concatenated into the upload base path without validation. No authentication and no user interaction are required (PR:N/UI:N), and default configurations are affected where these endpoints are reachable. The principal limiting factor is exposure rather than configuration: kkFileView is commonly deployed as an internal/back-office preview service, so internet-facing, unauthenticated reachability of the upload endpoints is the real-world precondition that gates mass exploitation. |
| Impact | Signals are mixed. The CVSS vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, base 7.5) describes a network-reachable, low-complexity, unauthenticated flaw with high integrity impact and no confidentiality or availability impact - consistent with arbitrary file/directory write. No EPSS score, no CISA KEV listing, and no confirmed public exploit code (POC) were provided in the input, so exploitation status is: no public exploit identified at time of analysis - although a public GitHub disclosure issue (sg-summer/cve/issues/4) exists. No SSVC decision data was supplied. The technical impact is serious: an unauthenticated attacker who can write files outside fileDir can typically escalate a CWE-22 path traversal to remote code execution by planting a webshell in a web-served directory, which in practice means the I:H rating understates real-world consequence (confidentiality/availability would follow a successful RCE even though the base vector marks them N). The key moderating factor is exposure: kkFileView is usually deployed as an internal document-preview microservice rather than an internet-facing application, and the vulnerable upload endpoints may not be enabled or reachable in every deployment. Net assessment: a genuine high-priority issue for any organization exposing kkFileView 5.0.0-5.0.2, but likely limited in blast radius due to the product's niche, often-internal deployment pattern rather than any lack of technical severity. |
| Exploit ScenarioDerived | An unauthenticated attacker locates a reachable kkFileView 5.0.0-5.0.2 instance and sends a crafted multipart upload request to the fileUpload endpoint with a 'path' parameter containing directory-traversal sequences (e.g. ../../), causing a file to be written outside the intended fileDir root - for example a JSP/webshell into a web-served directory - which is then requested to obtain code execution. A public disclosure issue exists on GitHub, but no confirmed weaponized exploit code was provided in the input data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
Unauthenticated directory traversal in kkFileView 5.0.0 through 5.0.2 lets remote attackers create arbitrary directories and write files outside the intended fileDir root via the fileUpload, createFolder, and existsFile endpoints, which concatenate an attacker-supplied 'path' parameter into the upload base path without any validation. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) confirms that no credentials and no user interaction are needed, and that the impact is integrity-only (C:N/A:N), meaning the attacker can plant content beyond the configured storage root but gains no direct read or availability effect. Exploitation is gated chiefly by exposure rather than configuration - kkFileView is typically deployed as an internal document-preview service - and no public exploit code was identified at time of analysis, so internet-facing, unauthenticated reachability of the upload endpoints is the real-world precondition for mass abuse.
RemediationAI
No vendor-released patch version is identified in the available advisory data, so the primary action is to treat exposure as the control that matters: block network access to the kkFileView upload/enumeration endpoints (fileUpload, createFolder, existsFile) from untrusted networks and place the service behind authentication at a reverse proxy or API gateway, accepting the trade-off that legitimate upload and folder-creation workflows used by clients will break unless a trusted ingress path is preserved. If the file-upload feature is not required, disable the upload functionality entirely or remove the upload endpoints from the exposed routing table. Run the service under a dedicated low-privilege OS account whose write permissions are confined to the intended fileDir tree, and mount the application container's filesystem read-only with only the fileDir path writable - this does not fix the traversal but limits where written files can land, at the cost of potentially breaking preview caching and temp-file generation. As a defense-in-depth measure, apply reverse-proxy or WAF rules that reject '..' and encoded traversal sequences in the 'path' parameter of multipart requests, while recognizing that WAF decoding differences make such rules bypassable and unsuitable as the sole mitigation. Monitor and audit for unexpected directories or files appearing outside fileDir, since detection of out-of-tree writes is the most reliable signal of attempted exploitation until an upstream fix is published; track the vendor project and the references at https://github.com/sg-summer/cve/issues/4 and https://nvd.nist.gov/vuln/detail/CVE-2026-95140 for a patched release and upgrade immediately once an exact fixed version is announced.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-22 (Improper Limitation of a Pathname to a Restricted Directory / 'Path Traversal'), implemented in FileController.java of the Java-based kkFileView document-preview application. The fileUpload, createFolder and existsFile handlers take a caller-controlled 'path' parameter from a crafted multipart request and concatenate it into the upload base path without normalization, canonicalization, or a check that the resolved absolute path remains beneath the configured fileDir root; classic '../' (or encoded equivalents) sequences therefore escape the storage directory and let the attacker dictate directory and file locations. This is a write/create primitive rather than a read primitive, which is consistent with the assessed integrity-only impact (I:H, C:N, A:N) - the traversal exposes the filesystem layout around the upload root but the immediate, verifiable effect is unauthorized directory creation and file placement. Note that the supplied CPE string (cpe:2.3:a:n/a:n/a:*) is an unpopulated placeholder and the EUVD affected-version field likewise reads 'n/a n/a', so exact product/version mapping rests on the description text and the 'Path Traversal' tag rather than on vendor CPE enumeration; the reference https://github.com/sg-summer/cve/issues/4 is the originating report and https://nvd.nist.gov/vuln/detail/CVE-2026-95140 is the NVD record mirrored by ENISA EUVD as EUVD-2026-93551.
Know when Kkfileview 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
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Unauthenticated network request with no user interaction (AV:N/AC:L/PR:N/UI:N); arbitrary file/directory write gives I:H, with C and A not directly impacted by the base flaw itself.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
3DescriptionCVE.org
kkFileView v5.0.0 through v5.0.2 contains a directory traversal vulnerability in FileController.java. The fileUpload, createFolder and existsFile endpoints accept a "path" parameter that is concatenated into the upload base path without validation, allowing unauthenticated attackers to create arbitrary directories and write arbitrary files outside the intended fileDir root via a crafted multipart request
Executive ViewAI
kkFileView versions 5.0.0 through 5.0.2 contain a high-severity unauthenticated directory-traversal flaw that lets remote attackers write files outside the configured storage root. Organizations using this internal document-preview service are affected because an exposed instance could allow attackers to plant or alter content in unintended locations, undermining document integrity and trust. No public exploit identified at time of analysis, and no vendor-released patch identified at time of analysis, so leadership should prioritize exposure reduction and monitoring.
No vendor-released patch identified at time of analysis; interim mitigations include restricting network access to trusted internal networks, placing the service behind an authenticated reverse proxy, running the service with least-privilege file system permissions, deploying WAF rules to block path traversal sequences in the 'path' parameter, and monitoring logs for unauthorized file creation in the fileDir root and surrounding directories.
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
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
More in Kkfileview
View allkkFileView 4.0 is vulnerable to Server-side request forgery (SSRF) via controller\OnlinePreviewController.java. Rated cr
kkFileView v4.1.0 was discovered to contain a Server-Side Request Forgery (SSRF) via the component cn.keking.web.control
kkFileView v4.0.0 was discovered to contain an arbitrary file deletion vulnerability via the fileName parameter at /cont
kkFileView v4.3.0 is vulnerable to Incorrect Access Control. Rated medium severity (CVSS 6.1), this vulnerability is rem
A vulnerability, which was classified as problematic, has been found in kkFileView. Rated medium severity (CVSS 6.1), th
kkFileView v4.1.0 is vulnerable to Cross Site Scripting (XSS) via the parameter 'errorMsg.'. Rated medium severity (CVSS
kkFileView v4.1.0 was discovered to contain multiple cross-site scripting (XSS) vulnerabilities via the urls and current
kkFileView v4.0.0 was discovered to contain a cross-site scripting (XSS) vulnerability via the url parameter at /control
Server-side request forgery in kkFileView 4.2.0 and later lets remote, unauthenticated attackers make the server fetch a
kkFileView 4.0 is vulnerable to Cross Site Scripting (XSS) via controller\ Filecontroller.java. Rated medium severity (C
A vulnerability was found in kkFileView 4.4.0. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploita
EUVD-2026-93551
GHSA-qj7c-283g-mmh2
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB