GHSA-68wg-qv6r-j4vp is a critical-severity (CVSS 9.8) SQL Injection vulnerability in usmanhalalit/pixie. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-68wg-qv6r-j4vp is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
SQL Injection in usmanhalalit/pixie
Real-World Exposure
usmanhalalit/pixie🐘usmanhalalit/pixieReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Pixie versions 1.0.x before 1.0.3, and 2.0.x before 2.0.2 allow SQL Injection in the limit() function due to improper sanitization.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | usmanhalalit/pixie | all versions | 1.0.3 |
| 🐘Packagist | usmanhalalit/pixie | ≥ 2.0.0&&< 2.0.2 | 2.0.2 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for usmanhalalit/pixie. 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 usmanhalalit/pixie to 1.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-68wg-qv6r-j4vp 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-68wg-qv6r-j4vp 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-68wg-qv6r-j4vp. 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-68wg-qv6r-j4vp in your dependencies?
O3 detects GHSA-68wg-qv6r-j4vp across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.