<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on Mateusz Najdek - blog</title><link>http://blog.najdek.me/tags/security/</link><description>Recent content in Security 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/security/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><item><title>Case Study: Responsible Disclosure of a Critical Path Traversal Vulnerability</title><link>http://blog.najdek.me/posts/responsible-disclosure-path-traversal/</link><pubDate>Mon, 08 Dec 2025 01:16:36 +0200</pubDate><author>mateusz@najdek.me (Mateusz Najdek)</author><guid>http://blog.najdek.me/posts/responsible-disclosure-path-traversal/</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 With a background in e-commerce engineering and system architecture, I have a habit of checking the &amp;ldquo;health&amp;rdquo; of the systems I interact with. During my first week of university, while browsing the Student Portal, my &amp;ldquo;security radar&amp;rdquo; went off.</description></item><item><title>PS5 Homebrew: Engineering a Local Autoload Chain in Lua</title><link>http://blog.najdek.me/posts/ps5-lua-autoloader/</link><pubDate>Mon, 30 Jun 2025 12:00:00 +0200</pubDate><author>mateusz@najdek.me (Mateusz Najdek)</author><guid>http://blog.najdek.me/posts/ps5-lua-autoloader/</guid><description>Context: In the console security scene, a &amp;ldquo;Jailbreak&amp;rdquo; is rarely a single file. It&amp;rsquo;s usually a complex chain of vulnerabilities. When the PS5 Lua exploit (based on the Artemis game engine) was released, it was a raw developer tool: it opened a network port and waited for a PC to send code.
This is fine for researchers, but terrible for usability. I engineered a full &amp;ldquo;Plug-and-Play&amp;rdquo; automation layer: an Autoloader that removes the PC dependency, and a graphical User Interface powered by an embedded HTTP server.</description></item></channel></rss>