How severe is GHSA-3c22-5j5m-4jq7?

GHSA-3c22-5j5m-4jq7 has a CVSS score of 8.7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-3c22-5j5m-4jq7?

GHSA-3c22-5j5m-4jq7 affects the following packages: github.com/forceu/gokapi (Go). Ecosystems affected: Go.

How do I fix GHSA-3c22-5j5m-4jq7?

Update github.com/forceu/gokapi to 2.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3c22-5j5m-4jq7 is resolved across your whole dependency graph.

How do I detect GHSA-3c22-5j5m-4jq7 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/forceu/gokapi. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-3c22-5j5m-4jq7 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-3c22-5j5m-4jq7?

O3 pinpoints whether GHSA-3c22-5j5m-4jq7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-3c22-5j5m-4jq7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-3c22-5j5m-4jq7 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-3c22-5j5m-4jq7?

GHSA-3c22-5j5m-4jq7 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 9th 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.

When was GHSA-3c22-5j5m-4jq7 published, and has it been updated?

GHSA-3c22-5j5m-4jq7 was published on March 5, 2026 and was last updated on March 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-3c22-5j5m-4jq7

HIGH

Gokapi has Stored XSS in SVG Hotlinks

Also known asCVE-2026-28683GO-2026-4612

Published

Mar 5, 2026

Updated

Mar 23, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk9th percentile+0.18%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐹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

Summary

If a malicious authenticated user uploads SVG and creates a hotlink for it, they achieve stored XSS.

Details

The hotlinking functionality fails to properly handle scripts included in the SVGs, allowing authenticated attackers with the ability to upload and hotlink file to execute arbitrary JS.

Issue found by aisafe.io

Impact

Authenticated attackers with the ability to upload and hotlink files can execute arbitrary JavaScript.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/forceu/gokapi`	all versions	2.2.3

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/forceu/gokapi to 2.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3c22-5j5m-4jq7 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-3c22-5j5m-4jq7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-3c22-5j5m-4jq7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary If a malicious authenticated user uploads SVG and creates a hotlink for it, they achieve stored XSS. ### Details The hotlinking functionality fails to properly handle scripts included in the SVGs, allowing authenticated attackers with the ability to upload and hotlink file to execute arbitrary JS. *Issue found by [aisafe.io](https://aisafe.io/)* ### Impact Authenticated attackers with the ability to upload and hotlink files can execute arbitrary JavaScript.

O3 Security · Impact-Aware SCA

Is GHSA-3c22-5j5m-4jq7 in your dependencies?

O3 detects GHSA-3c22-5j5m-4jq7 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works