Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify GROWI instance using Local file storage
-
ExploitRequest file attached to non-public page
-
ExecutionServer returns file without access check
-
ImpactRead confidential non-public content
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling File access restriction
MITRE ATT&CK
2 techniques across 1 tactic: 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 that the GROWI instance be configured with its file upload setting set to 'Local' (local filesystem storage) - this is the explicit precondition named in the description; instances using cloud/object storage (e.g., S3/GCS) backends are not stated to be affected. No authentication is required (PR:N) and no user interaction is needed (UI:N), and the attacker must have network reachability to the GROWI service. Impact is limited to disclosure of files attached to non-public pages; it does not grant write access or code execution. The configuration dependency on 'Local' storage is the primary factor limiting the exploitable population. |
| Impact | This is a moderate-severity information disclosure flaw (CVSS 3.0 base 5.3) whose real-world priority is bounded by its limited impact and conditional trigger. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) indicates a network-reachable, low-complexity, unauthenticated issue with only low confidentiality impact and no integrity or availability effect - consistent with reading files from non-public pages rather than full system compromise. No EPSS score was provided in the input, so exploitation-probability cannot be quantified here. There is no CISA KEV listing and no public exploit code referenced, so exploitation status is 'no public exploit identified at time of analysis.' No SSVC decision data was supplied. The key limiting factor is the configuration precondition: the flaw is only exploitable when GROWI's file upload setting is 'Local,' which narrows the exploitable population and argues against treating this as an indiscriminate, widespread threat. Net assessment: a legitimate but non-critical issue - patch in normal cycles unless the deployment uses 'Local' file storage and hosts sensitive non-public pages, in which case prioritize. Note that the description emphasizes access to non-public page files, while the CWE/tags cite Path Traversal and File Upload - the precise retrieval mechanism (direct object reference vs. traversal) is not fully disambiguated in the provided data. |
| Exploit ScenarioDerived | An attacker who can reach a GROWI instance over the network - without any credentials - requests files that are attached to private or otherwise non-public wiki pages and retrieves their contents directly. This works only when the instance stores uploads with the 'Local' file upload setting. No public proof-of-concept exploit was identified in the provided intelligence, and the low attack complexity means a correctly formed request is sufficient once the target configuration is known. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 05, 2026
Unauthenticated information disclosure in GROWI (CVSS 5.3) lets a network attacker read files attached to non-public pages when the instance's file upload setting is configured as 'Local' rather than a cloud or object-storage backend. Exploitation requires no credentials and no user interaction (PR:N/UI:N), but the impact is limited to low-confidentiality exposure of files that already reside on the server, with no write access or code execution. No public exploit code has been identified at time of analysis and the flaw is not reported as confirmed actively exploited (CISA KEV); the 'Local' storage precondition is the primary factor bounding the exposed population.
RemediationAI
Patch status is not confirmed from the available data: no vendor-released fixed version is identified in the supplied records, so administrators should consult the JVN advisory at https://jvn.jp/en/jp/JVN24352487/ and the vendor news page at https://growi.co.jp/news/47 for the current patch or upgrade guidance before planning changes. As a direct compensating control, change the file upload setting from 'Local' to a supported cloud or object-storage backend, which removes the configuration precondition; the trade-off is that existing local attachments may require migration and the deployment takes on an external storage dependency. Where that is not immediately possible, restrict network reachability to the GROWI service to trusted users and networks, accepting reduced accessibility, and audit non-public pages for attachments that may have been exposed. Because exploitation hinges on the 'Local' upload setting, verifying and altering that setting is the most reliable mitigation until a vendor fix is available.
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 issue is classified as CWE-552 (Files or Directories Accessible to External Parties), meaning an access-control gap on the file-serving path allows requests for attachments to succeed without the page-permission checks that should gate access to non-public wiki content. GROWI, an open-source wiki/knowledge-management platform maintained by GROWI, Inc., offers a file upload setting that can be configured as 'Local', storing attachments on the application server's filesystem instead of an external object store. In that configuration, the application does not properly enforce access control on those stored files, so a remote unauthenticated attacker who can reach the GROWI service and knows or guesses the file path can retrieve files belonging to restricted pages. The CPE cpe:2.3:a:growi,_inc.:growi:*:*:*:*:*:*:*:* indicates the vendor's product is treated as affected across the version range rather than at a single release, and the CVSS 3.0 vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N confirms network reachability, no privileges, no user interaction, and a confidentiality-only impact. Reporting originates from JPCERT/CC, with vendor and national CERT coordination reflected in the GROWI news item and the JVN advisory.
Know when Growi 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:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Network-reachable and unauthenticated (AV:N/PR:N) with a trivial request (AC:L); only file contents of non-public pages leak, so C:L and I:A:N.
Primary rating from Vendor (jpcert).
CVSS VectorVendor: jpcert
Lifecycle Timeline
1DescriptionCVE.org
An improper access control vulnerability exists in GROWI, which allow an unauthenticated attacker to read files contained in non-public pages of the affected product when the file upload setting is configured as "Local".
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.
Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
NoSQL injection vulnerability in GROWI versions prior to v4.2.20 allows a remote attacker to obtain and/or alter the inf
Cross-site request forgery (CSRF) vulnerability in GROWI v3.4.6 and earlier allows remote attackers to hijack the authen
Unauthenticated file disclosure in GROWI (all versions before 8.0.2) exposes private page attachments to any caller who
Remote denial of service via regular expression attack in GROWI allows unauthenticated network attackers to exhaust serv
Cross-user data exposure and tampering in GROWI v7.4.5 and earlier allows any authenticated user who learns a shared AI
Remote path traversal in GROWI v7.5.0 and earlier allows authenticated administrators to execute arbitrary EJS templates
Improper access control vulnerability in GROWI versions v4.2.2 and earlier allows a remote unauthenticated attacker to r
Directory traversal vulnerability in GROWI versions prior to v4.2.3 (v4.2 Series), GROWI versions prior to v4.1.12 (v4.1
Improper input validation in GROWI versions prior to v4.2.3 (v4.2 Series), GROWI versions prior to v4.1.12 (v4.1 Series)
GROWI v4.1.3 and earlier allow remote attackers to obtain information which is not allowed to access via unspecified vec
In WESEEK GROWI before 3.5.0, a remote attacker can obtain the password hash of the creator of a page by leveraging wiki
In WESEEK GROWI before 3.5.0, the site-wide basic authentication can be bypassed by adding a URL parameter access_token
EUVD-2026-92265
GHSA-h2pc-3fh7-hv26
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB