<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mateusz Najdek - blog</title><link>http://blog.najdek.me/</link><description>Recent content 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, 13 Dec 5000 12:00:00 +0200</lastBuildDate><atom:link href="http://blog.najdek.me/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>Engineering for Efficiency: Building a Custom Product Configurator to Automate Logistics</title><link>http://blog.najdek.me/posts/building-icup-custom-configurator/</link><pubDate>Sat, 15 Nov 2025 12:00:00 +0200</pubDate><author>mateusz@najdek.me (Mateusz Najdek)</author><guid>http://blog.najdek.me/posts/building-icup-custom-configurator/</guid><description>Context: In the world of personalized e-commerce on marketplaces like Allegro, the biggest bottleneck isn&amp;rsquo;t manufacturing—it&amp;rsquo;s matching the user&amp;rsquo;s design to the specific transaction without errors. Here is how I solved this problem with code.
The Problem: &amp;ldquo;Which &amp;lsquo;Anna&amp;rsquo; ordered this mug?&amp;rdquo; Selling custom products on Allegro (Poland&amp;rsquo;s largest marketplace) comes with a specific disconnect: the design tool lives outside the marketplace.
Most competitors solve this lazily: after designing a mug, they ask the user to &amp;ldquo;Type your Allegro Nickname&amp;rdquo; in a form.</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><item><title>Why I Built a Custom ERP in Native PHP (Scaling a Solo E-commerce Business)</title><link>http://blog.najdek.me/posts/building-custom-erp-native-php/</link><pubDate>Sat, 20 Jul 2024 14:00:00 +0200</pubDate><author>mateusz@najdek.me (Mateusz Najdek)</author><guid>http://blog.najdek.me/posts/building-custom-erp-native-php/</guid><description>Context: In the e-commerce world, the standard advice is &amp;ldquo;Don&amp;rsquo;t reinvent the wheel—use Shopify or BaseLinker.&amp;rdquo;
I ignored that advice. I run a personalized manufacturing business (printing custom t-shirts and mugs) as a one-man operation. When you are working alone, you don&amp;rsquo;t need &amp;ldquo;enterprise features&amp;rdquo;—you need a force multiplier. Here is how I built &amp;ldquo;Monmat Manager,&amp;rdquo; a proprietary ERP that allows me to process hundreds of orders solo.
The &amp;ldquo;Buy vs.</description></item><item><title>Carbon for F1TV: Real-Time Sync Engine for Multi-Window Playback</title><link>http://blog.najdek.me/posts/carbon-for-f1tv-realtime-sync/</link><pubDate>Sat, 06 Apr 2024 10:00:00 +0200</pubDate><author>mateusz@najdek.me (Mateusz Najdek)</author><guid>http://blog.najdek.me/posts/carbon-for-f1tv-realtime-sync/</guid><description>Context: F1TV is the official streaming service for Formula 1. While the content is great, the web player lacked a crucial feature for data nerds: Multi-View (watching the Main Feed + Driver Tracker + Onboard Cameras simultaneously).
Existing third-party tools relied on extracting stream URLs for external players, but this approach broke when F1TV implemented Widevine DRM. I engineered a solution that respects these security constraints while delivering a synchronized &amp;ldquo;Command Center&amp;rdquo; experience directly in the browser.</description></item></channel></rss>