GHSA-5fq8-3q2f-4m5g is a medium-severity (CVSS 6.5) vulnerability in django-user-sessions. O3 Security confirms whether GHSA-5fq8-3q2f-4m5g is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Session key exposure through session list in Django User Sessions
Real-World Exposure
django-user-sessionsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Impact
The views provided by django-user-sessions allow users to terminate specific sessions. The session key is used to identify sessions, and thus included in the rendered HTML. In itself this is not a problem. However if the website has an XSS vulnerability, the session key could be extracted by the attacker and a session takeover could happen.
Patches
Patch is under way.
Workarounds
Remove the session_key from the template.
References
None.
For more information
If you have any questions or comments about this advisory:
- Open an issue in Bouke/django-user-sessions
- Email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | django-user-sessions | all versions | 1.7.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django-user-sessions. 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 django-user-sessions to 1.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5fq8-3q2f-4m5g 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-5fq8-3q2f-4m5g 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-5fq8-3q2f-4m5g. 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-5fq8-3q2f-4m5g in your dependencies?
O3 detects GHSA-5fq8-3q2f-4m5g across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.