<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Xss on Mateusz Najdek - blog</title><link>http://blog.najdek.me/tags/xss/</link><description>Recent content in Xss on Mateusz Najdek - blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><managingEditor>mateusz@najdek.me (Mateusz Najdek)</managingEditor><webMaster>mateusz@najdek.me (Mateusz Najdek)</webMaster><lastBuildDate>Sat, 30 May 2026 01:10:22 +0200</lastBuildDate><atom:link href="http://blog.najdek.me/tags/xss/index.xml" rel="self" type="application/rss+xml"/><item><title>Case Study: Responsible Disclosure of a Critical Reflected XSS and Account Takeover Vulnerability</title><link>http://blog.najdek.me/posts/responsible-disclosure-reflected-xss-sso/</link><pubDate>Sat, 30 May 2026 01:10:22 +0200</pubDate><author>mateusz@najdek.me (Mateusz Najdek)</author><guid>http://blog.najdek.me/posts/responsible-disclosure-reflected-xss-sso/</guid><description>Disclaimer: The vulnerability described below was discovered during independent security research. It has been responsibly disclosed to the institution&amp;rsquo;s IT department and was patched immediately. All sensitive details (target name, URLs) have been redacted to maintain confidentiality.
Introduction Following up on my October 2025 discovery of a Path Traversal vulnerability in the Student Portal, I continued to keep an eye on the core infrastructure of the institution. Once you realize that legacy components exist in production, it is only logical to examine how the most critical gateways handle data.</description></item></channel></rss>