CVE-2025-48495

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.

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.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2025-48495 has a CVSS score of 5.4 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.0-20250530185940-65ddbc68fbfd); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-48495? CVE-2025-48495 is a medium-severity cross-site scripting (XSS) vulnerability in github.com/forceu/gokapi (go), affecting versions >= 1.0.1, <= 1.9.6. It is fixed in 0.0.0-20250530185940-65ddbc68fbfd. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2025-48495? CVE-2025-48495 has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/forceu/gokapi are affected by CVE-2025-48495? github.com/forceu/gokapi (go) versions >= 1.0.1, <= 1.9.6 is affected.
4. Is there a fix for CVE-2025-48495? Yes. CVE-2025-48495 is fixed in 0.0.0-20250530185940-65ddbc68fbfd. Upgrade to this version or later.
5. Is CVE-2025-48495 exploitable, and should I be worried? Whether CVE-2025-48495 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-48495 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-48495? Upgrade github.com/forceu/gokapi to 0.0.0-20250530185940-65ddbc68fbfd or later.