/

CVE-2026-28276

Severity:

HIGH RISK

(7.5)

Improper Access Control / Information Disclosure

CVE-2026-28276

Analyzed

Vulnerability type

Category:

Improper Access Control / Information Disclosure

CWE:

CWE-200, CWE-284, CWE-862

Impact:

Sensitive 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

Initiative, a self-hosted project management platform, exposed uploaded documents via a publicly accessible /uploads/ directory with no authentication or authorization checks.

Anyone who knows or can guess the file URL could access those documents, including unauthenticated users, potentially leading to disclosure of sensitive project data and attachments.

Affected context

This vulnerability affects Initiative deployments where the application serves user-uploaded files directly from a web-accessible /uploads/ directory.

The issue manifests when files are stored under predictable or enumerable paths and delivered by the web server without being gated through the application's authentication and authorization logic.

It is most concerning in environments where users upload potentially sensitive content such as project documents, contracts, internal diagrams, or customer data, and where external or untrusted users can reach the Initiative HTTP endpoint.

Exploit preconditions

  • Attack surface: Publicly reachable HTTP endpoint exposing the /uploads/ directory or equivalent file path.
  • Required access: Network access to the Initiative instance (no authentication required to exploit once a file URL is known or guessed).
  • Trigger point: Direct HTTP GET requests to uploaded file URLs under /uploads/ (e.g., by following a shared link, guessing file names, or deriving URLs from leaked references).
  • Why exploitation is possible: The file serving mechanism bypasses or omits access control checks, treating uploaded content as static assets rather than protected resources, so the web server returns files without verifying user identity or permissions.

Why this happens

The underlying issue is an improper access control design for user-uploaded content.

Uploaded documents are stored in a location that is directly served by the web server, and requests to these paths do not flow through the application's authorization layer.

This maps primarily to CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), with related aspects of CWE-284 (Improper Access Control) and CWE-862 (Missing Authorization), because the system fails to enforce per-request checks to confirm that the requester is authenticated and authorized to access a given document.

Conceptually, the pattern is: "treating sensitive user content as public static files" rather than as protected resources requiring controlled access.

Potential impact

  • Unauthorized access to uploaded documents containing sensitive business or personal information.
  • Exposure of internal project details, project plans, roadmaps, or incident-related files.
  • Disclosure of confidential client data, contracts, or financial records managed within projects.
  • Facilitation of targeted social engineering or phishing using leaked internal documents.
  • Regulatory or contractual non-compliance if protected or personal data is exposed.

General mitigation guidance

Mitigation typically focuses on re-aligning file storage and serving mechanisms with the application's access control model and treating uploaded files as protected resources by default.

Recommended patterns include:

  • Route all access to uploaded files through an authenticated application endpoint that performs both authentication and fine-grained authorization checks before returning content.
  • Store uploads outside the directly web-accessible document root (e.g., on a private filesystem path or object storage bucket) so that files cannot be fetched without going through application logic.
  • Use unpredictable, non-enumerable identifiers for stored files (e.g., cryptographically strong random IDs) to reduce the risk of guessing, while not relying on obscurity as the primary control.
  • Apply role- and project-based access control for documents, ensuring files are linked to the same authorization rules as the projects or entities they belong to.
  • Adopt a "private by default" approach for uploaded content, requiring explicit configuration or sharing actions to make any file accessible to broader audiences.

How teams detect issues like this

Effective detection emphasizes reviewing how files are stored and served, combined with automated checks around access control.

Possible approaches:

  • Static analysis and code review to identify:
  • Direct links or references from database records to web-accessible file paths (e.g., /uploads/...) that bypass controller logic.
  • File-serving routes that skip authentication or authorization middleware.
  • Configuration review of web servers (e.g., Nginx, Apache) to detect directories under the document root that contain user-uploaded content without access restrictions.
  • Security testing and QA that:
  • Attempts to access uploaded files in an incognito browser or logged-out session.
  • Verifies that access is denied for users who are not part of the relevant project or permission group.
  • Integration of automated security scanning tools that flag static file directories whose contents are influenced by user uploads, or that detect missing authorization checks for download endpoints.

Sources

SourceLink
github.comgithub.com/Morelitea/initiative/releases/tag/v0.32.2
github.comgithub.com/Morelitea/initiative/security/advisories/GHSA-w34j-fx72-h2pq

Frequently asked

questions

Yes. Any remote user with network access to the Initiative instance can exploit the vulnerability if they know or can discover URLs under the /uploads/ directory, without needing an account.

No. The core issue is that uploaded files are served without authentication or authorization checks. An unauthenticated user, including one in an incognito session, can access files directly if they have the link or can guess the path.

The safest approach is to remove direct public access to the upload directory and ensure that all file downloads go through an application layer that performs robust authentication and context-aware authorization. Additionally, storing uploads outside the public web root and only streaming them via controlled endpoints reinforces this pattern.

Design file handling with a "protected resource" mindset: treat uploaded content as private by default, systematically enforce access control on every file request, and ensure architecture and deployment configurations (web server, storage) cannot bypass these checks. Regular security reviews and automated tests that attempt file access from unauthenticated contexts help catch regressions early.

Find out what's already
exploitable in your codebase.