Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-80191 – Unauthenticated Access to Private Page Attachments – GROWI before 8.0.2

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-80191 is a missing authorization vulnerability (CWE-862) in GROWI, the open-source wiki platform, affecting all versions before 8.0.2. The attachment retrieval logic only enforces the page-viewer permission check when a request carries an authenticated session, allowing unauthenticated attackers who possess an attachment identifier to download files attached to private pages. The issue carries a HIGH severity rating.

Technical details

  • Root cause: The attachment retrieval handler (retrieveAttachmentFromIdParam) only runs the permission check when the requesting user is non-null; requests with no session bypass the check entirely.
  • Trigger conditions: An attacker needs only a valid attachment identifier — no authentication, session, or prior access to the page is required.
  • Attack vector: Network-reachable, unauthenticated HTTP requests to the /attachment/:id and /download/:id routes, which take the attachment identifier directly from the URL path.
  • Impact: Disclosure of files attached to private pages, including cases where a user’s access to the page was later revoked, or where the identifier was previously exposed elsewhere. No integrity or availability impact is associated with this flaw.

Affected software

  • GROWI: all versions prior to 8.0.2

Severity

  • CVSS v4.0: 8.7 (HIGH) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1: 7.5 (HIGH) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade GROWI to version 8.0.2 or later, which enforces the permission check for both authenticated and unauthenticated requests, exempting only files already bound to a valid share link for the requested page.
  • If immediate patching is not possible: Restrict network access to GROWI instances (e.g., placing them behind VPN or IP allow-listing), rotate/regenerate attachment identifiers where feasible, and monitor logs for unauthenticated requests to /attachment/:id and /download/:id.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: GROWI
  • Raw response body: href="https://growi.org/" class="...link-growi-org...", "growi_is_under_maintenance":, "transfer_data_to_this_growi":, github.com/growilabs/growi/issues/193, GROWI.5.0_new_schema together with docs.growi.org/ja/admin-guide/upgrading/50x.html, and link-growi-org together with "growi_is_under_maintenance" or "transfer_data_to_this_growi"

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge