CVE-2026-28683
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 · uneditedGokapi is a self-hosted file sharing server with automatic expiration and encryption support. Prior to version 2.2.3, if a malicious authenticated user uploads SVG and creates a hotlink for it, they can achieve stored XSS. 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 · high confidenceStored XSS vulnerability in Gokapi versions prior to 2.2.3 allows authenticated users to upload malicious SVG files containing embedded JavaScript. When the SVG is accessed via a hotlink, the script executes in the victim's browser, potentially allowing session hijacking or actions as the victim.
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< 2.2.3CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Gokapi versionLocate the installed Gokapi instance and check its version number (typically visible in the web UI footer, admin panel, or by querying the running service)Affected if The installed version is earlier than 2.2.3
-
Confirm authenticated user upload is enabledCheck Gokapi configuration for user registration or admin-created user accounts that can upload filesAffected if Authenticated users or public user registration is enabled, allowing file uploads
-
Verify SVG upload capabilityCheck if the upload functionality accepts SVG file types by attempting to upload a test SVG or reviewing upload restrictions in the configurationAffected if SVG files can be uploaded to the system
-
Confirm hotlinking is enabledExamine Gokapi settings for hotlink/remote access functionality that allows direct URL access to uploaded filesAffected if Hotlinking or direct file URL access is enabled, allowing external access to uploaded files
-
Check SVG Content-Type header configurationInspect how Gokapi serves SVG files - whether it uses application/xml, image/svg+xml, or another type - by accessing a uploaded SVG via its direct URL and inspecting the response headersAffected if SVG files are served without proper Content-Type headers that prevent script execution, or the headers allow script execution in browsers
A user is affected if their Gokapi installation is version 2.2.3 or earlier, authenticated uploads are permitted, SVG files can be uploaded, hotlinking is enabled, and SVG files are served with Content-Type headers that permit script execution in browsers.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.2.3
Upgrade to Gokapi version 2.2.3. Additionally, configure SVG content to be served with proper Content-Type headers (application/xml or image/svg+xml) that prevent script execution, or implement SVG sanitization to strip potentially dangerous elements.
2.2.3
- Backup your current Gokapi installation and all user data
- Stop the running Gokapi service
- Download Gokapi version 2.2.3 from the official GitHub repository (github.com)
- Replace the existing Gokapi binary/application files with the new version 2.2.3
- Restart the Gokapi service
- Verify the upgrade was successful by logging in and confirming the application functions normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28683 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-28683 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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