How severe is GHSA-95rc-wc32-gm53?

No CVSS score has been assigned to GHSA-95rc-wc32-gm53 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-95rc-wc32-gm53?

GHSA-95rc-wc32-gm53 affects the following packages: github.com/forceu/gokapi (Go), github.com/forceu/gokapi (Go). Ecosystems affected: Go.

How do I fix GHSA-95rc-wc32-gm53?

A fix is available for GHSA-95rc-wc32-gm53; check the affected-versions list above or the advisory for the patched release of github.com/forceu/gokapi, then make sure no transitive dependency still pins the vulnerable range.

How do I detect GHSA-95rc-wc32-gm53 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/forceu/gokapi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-95rc-wc32-gm53 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-95rc-wc32-gm53 actively exploited in the wild?

No public exploit code has been indexed for GHSA-95rc-wc32-gm53 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-95rc-wc32-gm53?

GHSA-95rc-wc32-gm53 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 7th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-95rc-wc32-gm53?

GHSA-95rc-wc32-gm53 is classified as Cross-site Scripting (XSS) (CWE-79), CWE-87 (CWE-87). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-95rc-wc32-gm53 published, and has it been updated?

GHSA-95rc-wc32-gm53 was published on June 3, 2025 and was last updated on August 26, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

Gokapi vulnerable to stored XSS via uploading file with malicious file nameGHSA-95rc-wc32-gm53

Fix: Forceu/Gokapi@343cc56

GHSA-95rc-wc32-gm53 is a Cross-site Scripting (XSS) vulnerability in github.com/forceu/gokapi. A fix is available for github.com/forceu/gokapi — see the affected versions and patch details below.

Also known asCVE-2025-48494GO-2025-3737

Published

Jun 3, 2025

Updated

Aug 26, 2025

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-95rc-wc32-gm53.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs7th percentile — riskier than 7% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐹github.com/forceu/gokapi🐹github.com/forceu/gokapi

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

When using end-to-end encryption, a stored XSS 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.

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 disable end-to-end encryption.

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/forceu/gokapi`	≥ 1.0.1	No fix
🐹Go	`github.com/forceu/gokapi`	all versions	0.0.0-20250530191232-343cc566cfd7`go get github.com/forceu/gokapi@v0.0.0-20250530191232-343cc566cfd7`

Affected Products

1 product · 3 configurations

Application

gokapiforceu

< 2.0.0

1 version

2.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/forceu/gokapi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for GHSA-95rc-wc32-gm53; check the affected-versions list above or the advisory for the patched release of github.com/forceu/gokapi, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Impact When using end-to-end encryption, a stored XSS 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. 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 pos

O3 Security · Impact-Aware SCA

Is GHSA-95rc-wc32-gm53 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works