GHSA-3fr8-mwpp-8h9p is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in tileserver-gl. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-3fr8-mwpp-8h9p is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Cross-site scripting in TileServer GL
Real-World Exposure
tileserver-glReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
An issue was discovered in server.js in TileServer GL through 3.0.0. The content of the key GET parameter is reflected unsanitized in an HTTP response for the application's main page, causing reflected XSS.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | tileserver-gl | all versions | 3.1.0 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Tileserver-gl 3.0.0 - 'key' Reflected Cross-Site Scripting (XSS)
by Akash Chathoth · Apr 15, 2021
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tileserver-gl. 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 tileserver-gl to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3fr8-mwpp-8h9p 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-3fr8-mwpp-8h9p 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-3fr8-mwpp-8h9p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-3fr8-mwpp-8h9p in your dependencies?
O3 detects GHSA-3fr8-mwpp-8h9p across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.