/

CVE-2026-80191

Severity:

HIGH RISK

(7.5)

Missing Authorization (CWE-862) in GROWI Attachments

CVE-2026-80191

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Unauthorized Information Disclosure

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

GROWI may return private page attachments to unauthenticated requests when the caller supplies a known attachment identifier. The risk arises when the attachment routes skip page-viewer authorization for requests without a valid session, allowing unauthorized disclosure of files from restricted pages.

Affected context

The issue occurs in GROWI attachment retrieval and download routes when authorization is applied only after an authenticated user has been identified. Deployments are at risk when an attachment identifier remains accessible after a user's page permissions are removed, or when an identifier has previously appeared in a location accessible to an unauthorized party. A valid share-link workflow may represent a separate authorization context.

Exploit preconditions

  • Attack surface: Attachment retrieval and download endpoints - Required access: No authenticated session is required, but the requester

must know or obtain a valid attachment identifier

  • Trigger point: A request to an attachment route containing the identifier - Why exploitation is possible: The page-viewer permission check is

conditionally bypassed when the request user is absent, so possession of

the identifier can be treated as sufficient to retrieve the file

Why this happens

The underlying bug is an authorization control-flow error mapped to CWE-862, Missing Authorization. The handler evaluates whether to enforce page-level access rules based on the presence of an authenticated user, rather than enforcing authorization for every request and then separately handling explicitly authorized sharing mechanisms. This creates an unauthenticated path in which an object identifier is accepted without verifying access to the page that owns the attachment.

Potential impact

  • Unauthorized users may retrieve attachments from private pages
  • Confidential documents or other sensitive files could be disclosed
  • Previously authorized users may retain access after their permissions are revoked
  • Organizations may face privacy, compliance, or data-exposure consequences

General mitigation guidance

Mitigation generally centers on enforcing authorization consistently for authenticated and unauthenticated requests. Attachment access should default to deny unless a current page-view permission or a narrowly scoped, valid share authorization has been established. The attachment identifier should be treated as an object reference rather than proof of access, and access decisions should be bound to the owning page and current policy state. Authorization logic should be centralized to reduce divergent route behavior, while service identities and storage access should use least privilege. Where practical, opaque or short-lived references, revocation checks, and minimized exposure of identifiers can further reduce trust in caller-supplied values.

How teams detect issues like this

Detection approaches include static analysis for authorization checks guarded by nullable-user conditions, code review of every file-serving route, and tests that request private-page objects without a session. Security tests should also verify that access is revoked when page permissions change and that share links are validated independently of ordinary attachment access. Policy enforcement can require centralized authorization middleware for object retrieval endpoints, and automated review tools may help identify routes that return protected resources before an access decision is made.

Sources

SourceLink
github.comgithub.com/growilabs/growi
github.comgithub.com/growilabs/growi/blob/v8.0.1/apps/app/src/server/routes/attachment/get.ts
github.comgithub.com/growilabs/growi/pull/11756
github.comgithub.com/growilabs/growi/releases/tag/v8.0.2
vulncheck.comvulncheck.com/advisories/growi-before-8.0.2-missing-authorization-on-attachment-retrieval-for-unauthenticated-requests

Frequently asked

questions

Yes, where the affected attachment routes are reachable over the network.

The requester generally does not need to authenticate, but must know or

obtain a valid attachment identifier.

Not necessarily. The vulnerable path is specifically associated with

requests that do not carry an authenticated session. Possession of an

attachment identifier is the important prerequisite.

Enforce the owning page's current authorization policy for every attachment

request, using a deny-by-default model. Handle valid share links as a

separately verified authorization mechanism rather than skipping checks for

anonymous callers.

Apply centralized authorization middleware to file-serving routes, test both

authenticated and anonymous access paths, avoid treating object identifiers

as authorization tokens, and include permission-revocation cases in

regression and security testing.

Find out what's already
exploitable in your codebase.