Skip to main content

GROWI CVE-2026-100727

| EUVDEUVD-2026-92265 MEDIUM
Files or Directories Accessible to External Parties (CWE-552)
2026-10-05 jpcert GHSA-h2pc-3fh7-hv26
6.9
CVSS 4.0 · Vendor: jpcert
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify GROWI instance using Local file storage
  2. Exploit
    Request file attached to non-public page
  3. Execution
    Server returns file without access check
  4. Impact
    Read 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.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

GROWI 0 <v7.5.5

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

Vendor (jpcert) PRIMARY 6.9 MEDIUM
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
vuln.today AI 5.3 MEDIUM

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.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (jpcert).

CVSS VectorVendor: jpcert

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
CVSS changed
Oct 05, 2026 - 07:22 NVD
5.3 (MEDIUM) 6.9 (MEDIUM)

DescriptionCVE.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

EPSS Score
0.2%
Top 87% exploitable
Prevalence
Low
GROWI is a niche open-source wiki, strong footprint mainly in Japan
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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.

More in Growi

View all
CVE-2021-20736 CRITICAL
9.1 Jun 22

NoSQL injection vulnerability in GROWI versions prior to v4.2.20 allows a remote attacker to obtain and/or alter the inf

CVE-2019-5968 HIGH
8.8 Jul 05

Cross-site request forgery (CSRF) vulnerability in GROWI v3.4.6 and earlier allows remote attackers to hijack the authen

CVE-2026-80191 HIGH
8.7 Aug 25

Unauthenticated file disclosure in GROWI (all versions before 8.0.2) exposes private page attachments to any caller who

CVE-2026-41040 HIGH
8.7 Apr 23

Remote denial of service via regular expression attack in GROWI allows unauthenticated network attackers to exhaust serv

CVE-2026-25083 HIGH
8.7 Mar 16

Cross-user data exposure and tampering in GROWI v7.4.5 and earlier allows any authenticated user who learns a shared AI

CVE-2026-41951 HIGH
8.6 May 11

Remote path traversal in GROWI v7.5.0 and earlier allows authenticated administrators to execute arbitrary EJS templates

CVE-2021-20670 HIGH
7.5 Mar 10

Improper access control vulnerability in GROWI versions v4.2.2 and earlier allows a remote unauthenticated attacker to r

CVE-2020-5683 HIGH
7.5 Dec 16

Directory traversal vulnerability in GROWI versions prior to v4.2.3 (v4.2 Series), GROWI versions prior to v4.1.12 (v4.1

CVE-2020-5682 HIGH
7.5 Dec 16

Improper input validation in GROWI versions prior to v4.2.3 (v4.2 Series), GROWI versions prior to v4.1.12 (v4.1 Series)

CVE-2020-5676 HIGH
7.5 Dec 03

GROWI v4.1.3 and earlier allow remote attackers to obtain information which is not allowed to access via unspecified vec

CVE-2019-13338 HIGH
7.5 Jul 09

In WESEEK GROWI before 3.5.0, a remote attacker can obtain the password hash of the creator of a page by leveraging wiki

CVE-2019-13337 HIGH
7.5 Jul 09

In WESEEK GROWI before 3.5.0, the site-wide basic authentication can be bypassed by adding a URL parameter access_token

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy