Approved changes feed: RSS · Atom

cpe:2.3:a:forceu:gokapi:2.0.0:beta2:*:*:*:*:*:*

part: a version: 2.0.0 update: beta2

VendorForceu (43276b1b-0e59-5cb1-8756-bbffe112160c)
ProductGokapi (be9a5009-6c08-558a-baf1-52a69112144c)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:github/forceu/gokapi purl2cpe 2026-06-01 10:15:43.151527
pkg:golang/github.com/forceu/gokapi purl2cpe 2026-06-01 10:15:43.151529

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2025-48495 vulnerable 2026-06-08 07:27:15.998783 Gokapi has stored XSS vulnerability in friendly name for API keys
Gokapi is a self-hosted file sharing server with automatic expiration and encryption support. By renaming the friendly name of an API key, an authenticated user could inject JS into the API key overview, which would also be executed when another user clicks on his API tab. Prior to version 2.0.0, there was no user permission system implemented, therefore all authenticated users were already able to see and modify all resources, even if end-to-end encrypted, as the encryption key had to be the same for all users of versions prior to 2.0.0. If a user is the only authenticated user using Gokapi, they are not affected. This issue has been fixed in v2.0.0. A workaround would be to not open the API page if it is possible that another user might have injected code.
Published: 2025-06-02T11:08:07.017Z
Updated: 2025-06-02T16:51:10.394Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-48494 vulnerable 2026-06-08 07:27:15.998197 Gokapi vulnerable to stored XSS via uploading file with malicious file name
Gokapi is a self-hosted file sharing server with automatic expiration and encryption support. When using end-to-end encryption, a stored cross-site scripting vulnerability can be exploited by uploading a file with JavaScript code embedded in the filename. After upload and every time someone opens the upload list, the script is then parsed. Prior to version 2.0.0, there was no user permission system implemented, therefore all authenticated users were already able to see and modify all resources, even if end-to-end encrypted, as the encryption key had to be the same for all users using a version prior to 2.0.0. If a user is the only authenticated user using Gokapi, they are not affected. This issue has been fixed in v2.0.0. A possible workaround would be to disable end-to-end encryption.
Published: 2025-06-02T11:03:52.689Z
Updated: 2025-06-02T13:05:27.835Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.