<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Php on Mateusz Najdek - blog</title><link>http://blog.najdek.me/tags/php/</link><description>Recent content in Php 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/php/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>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></channel></rss>