dbcve.org
GokapiApplication · Forceu

CVE-2026-28682

MEDIUM · 6.4 CVSS v3.1 Published 2026-03-06
Fix available
A fix is available. Upgrade to 2.2.3 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable 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
Gokapi is a self-hosted file sharing server with automatic expiration and encryption support. Prior to version 2.2.3, the upload status SSE implementation on /uploadStatus publishes global upload state to any authenticated listener and includes file_id values that are not scoped to the requesting user. This issue has been patched in version 2.2.3.

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 · moderate confidence

The /uploadStatus SSE endpoint in Gokapi versions prior to 2.2.3 publishes upload status information for ALL users to any authenticated listener, exposing file_id values through an insecure direct object reference. This allows any authenticated user to view metadata about uploads they did not initiate.

MitigationUpgrade to Gokapi version 2.2.3 which implements proper user scoping for file_id values in the upload status SSE endpoint.

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
GokapiApplication
Affected:< 2.2.3

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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 Gokapi installation
    Check for Gokapi web application by accessing the application's login or main page and identifying it as Forceu Gokapi
    Affected if Gokapi is present in the environment
  2. Determine installed Gokapi version
    Locate the version information in the Gokapi web interface (typically in the footer, settings, or about page) or check the binary/docker image version tag, then compare to 2.2.3
    Affected if The installed version is earlier than 2.2.3
  3. Verify /uploadStatus endpoint accessibility
    Attempt to access the /uploadStatus SSE endpoint with valid authentication credentials to confirm it is reachable
    Affected if The endpoint responds with server-sent events data when accessed with authenticated credentials
  4. Confirm IDOR exposure exists
    With an authenticated user account, observe the /uploadStatus SSE stream and check if it contains file_id values for uploads initiated by OTHER users
    Affected if The SSE stream contains file metadata for uploads not created by the authenticated user

User is affected if running Gokapi version below 2.2.3 and the /uploadStatus endpoint is accessible to authenticated users, exposing file_id values from other users' uploads.

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 2.2.3 or later
Fixed in 2.2.3
Interim mitigation

Upgrade to Gokapi version 2.2.3 which implements proper user scoping for file_id values in the upload status SSE endpoint.

Recommended fix High confidence

2.2.3

  1. 1. Back up the current Gokapi installation, configuration files, and data directory
  2. 2. Download Gokapi version 2.2.3 from the official GitHub releases repository
  3. 3. Stop the currently running Gokapi service
  4. 4. Replace the existing Gokapi binaries with the new version 2.2.3
  5. 5. Restore any custom configuration from the backup
  6. 6. Start the Gokapi service
  7. 7. Verify the application is running correctly and test that /uploadStatus now properly scopes file_id values to the requesting user

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

Fix this in Gokapi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28682 — 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-28682 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