https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 19 Oct 2026 18:59:57 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-36443 EUVD-2026-36443 https://cve.radiocsirt.org/vuln/euvd-2026-36443 https://cve.radiocsirt.org/vuln/fkie_cve-2020-5224 <p>In Django User Sessions (django-user-sessions) before 1.7.1, the views provided 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.</p> <p>In Django User Sessions (django-user-sessions) before 1.7.1, the views provided 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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2020-5224 https://cve.radiocsirt.org/vuln/ghsa-5fq8-3q2f-4m5g <p><strong>Affected:</strong> PyPI: django-user-sessions</p> <p>### 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.</p> <p>### Patches Patch is under way.</p> <p>### Workarounds Remove the session_key from the template.</p> <p>### References _None._</p> <p>### For more information If you have any questions or comments about this advisory: * Open an issue in [Bouke/django-user-sessions](https://github.com/Bouke/django-user-sessions/issues) * Email us at [bouke@haarsma.eu](mailto:bouke@haarsma.eu)</p> <p><strong>Affected:</strong> PyPI: django-user-sessions</p> <p>### 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.</p> <p>### Patches Patch is under way.</p> <p>### Workarounds Remove the session_key from the template.</p> <p>### References _None._</p> <p>### For more information If you have any questions or comments about this advisory: * Open an issue in [Bouke/django-user-sessions](https://github.com/Bouke/django-user-sessions/issues) * Email us at [bouke@haarsma.eu](mailto:bouke@haarsma.eu)</p> https://cve.radiocsirt.org/vuln/ghsa-5fq8-3q2f-4m5g https://cve.radiocsirt.org/vuln/gsd-2020-5224 gsd-2020-5224 https://cve.radiocsirt.org/vuln/gsd-2020-5224 https://cve.radiocsirt.org/vuln/pysec-2020-230 <p><strong>Affected:</strong> PyPI: django-user-sessions</p> <p>In Django User Sessions (django-user-sessions) before 1.7.1, the views provided 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.</p> <p><strong>Affected:</strong> PyPI: django-user-sessions</p> <p>In Django User Sessions (django-user-sessions) before 1.7.1, the views provided 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.</p> https://cve.radiocsirt.org/vuln/pysec-2020-230