dbcve.org
InitiativeApplication · Morelitea

CVE-2026-28276

HIGH · 7.5 CVSS v3.1 Published 2026-02-26
Fix available
A fix is available. Upgrade to 0.32.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Initiative is a self-hosted project management platform. An access control vulnerability exists in Initiative versions prior to 0.32.2 where uploaded documents are served from a publicly accessible /uploads/ directory without any authentication or authorization checks. Any uploaded file can be accessed directly via its URL by unauthenticated users (e.g., in an incognito browser session), leading to potential disclosure of sensitive documents. The problem was patched in v0.32.2, and the patch was further improved on in 032.4.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The /uploads/ directory in Initiative versions prior to 0.32.2 serves uploaded files without any authentication or authorization checks, allowing unauthenticated users to directly access sensitive documents via URL. This is an authorization bypass vulnerability where the file serving mechanism fails to validate user identity before returning file content.

MitigationUpgrade to version 0.32.2 or later (0.32.4 preferred) which contains the patch. Additionally, implement proper authentication and authorization middleware for all file serving endpoints to ensure only authorized users can access uploaded documents.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
InitiativeApplication
Affected:< 0.32.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Morelitea Initiative installation
    Locate the Morelitea Initiative application files and identify the installed version by checking version metadata files (such as version.txt, package.json, or the main application binary metadata)
    Affected if The application is Morelitea Initiative and the version is below 0.32.2
  2. Verify /uploads/ endpoint exists
    Check if the /uploads/ directory or endpoint is configured in the web server or application configuration
    Affected if The /uploads/ endpoint exists in the application routing or web server configuration
  3. Test unauthenticated file access
    Send an HTTP GET request to the /uploads/ path without providing any authentication credentials (e.g., curl -v http://target/uploads/testfile)
    Affected if The server returns file content without redirecting to a login page or returning an authentication error (401/403)
  4. Confirm file serving without authorization
    Upload a test file through any available upload mechanism, then attempt to access that file via direct URL without authentication
    Affected if The uploaded file is served successfully to an unauthenticated user, indicating missing authorization checks

A user is affected if they are running Morelitea Initiative version 0.32.2 or lower AND the /uploads/ endpoint is accessible to unauthenticated users, allowing direct file retrieval without any login or authorization validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.32.2 or later
Fixed in 0.32.2
Interim mitigation

Upgrade to version 0.32.2 or later (0.32.4 preferred) which contains the patch. Additionally, implement proper authentication and authorization middleware for all file serving endpoints to ensure only authorized users can access uploaded documents.

Recommended fix High confidence

Upgrade to Initiative v0.32.4

  1. Backup your existing Initiative installation and database before proceeding
  2. Download Initiative v0.32.4 (the version with the improved patch) from the official GitHub repository
  3. Replace the existing Initiative files with the new version, preserving your configuration and data directories
  4. Restart the Initiative service/application
  5. Verify that /uploads/ directory now requires authentication by attempting to access an uploaded file in an incognito browser session
  6. Confirm the access control fix is working - authenticated users should be able to access their own uploads while unauthenticated access is blocked

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Initiative Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28276 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28276 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data