Gokapi has stored XSS vulnerability in friendly name for API keys

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

4.8 · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:L · score source

EPSS

• CVE-2025-48495: 0.14% estimated exploitation activity in the next 30 days; percentile 3.54 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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. With the affected versions <v2.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 with <v2.0. Nethertheless with XSS, other attack vectors like redirection or crypto mining would be possble. Patches This CVE has been fixed in v2.0.0 Workarounds If you are the only authenticated user using Gokapi, you are not affected. A workaround would be to not open the API page if you suspect that another user might have injected code.

Published by the source

3 Jun 2025, 06:27 UTC

Last modified by the source

26 Aug 2025, 20:11 UTC

Source last checked

26 Oct 2026, 15:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4xg4-54hm-9j77

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-48495

Advisory: Gokapi has stored XSS vulnerability in friendly name for API keys
IDs: CVE-2025-48495, GHSA-4xg4-54hm-9j77
Record: https://patchnext.com/advisories/cve-2025-48495 (revision 1, source checked 26 Oct 2026, 15:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/forceu/gokapi 0.0.0-20250530185940-65ddbc68fbfd. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/forceu/gokapi: affected >= 1.0.1, <= 1.9.6; < 0.0.0-20250530185940-65ddbc68fbfd; fixed in 0.0.0-20250530185940-65ddbc68fbfd

## Suggested inspection (read-only)
- Go github.com/forceu/gokapi: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/forceu/gokapi.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4xg4-54hm-9j77 (GitHub-reviewed advisory GHSA-4xg4-54hm-9j77 lists affected ranges: Go github.com/forceu/gokapi >=1.0.1 =0 <0.0.0-20250530185940-65ddbc68fbfd)

Commands are suggestions: review each one before running it.