<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Markdown on idkwhoiamx999</title><link>https://blog-idkwhoiamx999.netlify.app/tags/markdown/</link><description>Recent content in Markdown on idkwhoiamx999</description><generator>Hugo</generator><language>en</language><copyright>© 2026, idkwhoiamx999</copyright><lastBuildDate>Mon, 06 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog-idkwhoiamx999.netlify.app/tags/markdown/index.xml" rel="self" type="application/rss+xml"/><item><title>When Missing Rate Limiting Leads to a Critical Authentication Finding: A Real-World Case Study</title><link>https://blog-idkwhoiamx999.netlify.app/post/post1/</link><pubDate>Mon, 06 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog-idkwhoiamx999.netlify.app/post/post1/</guid><description>&lt;p&gt;Hey It’s been quite a while since my last article, but I’m excited to start publishing consistently again, covering web application security, bug bounty research, CTFs, penetration testing, and the lessons I learn along the way.&lt;/p&gt;
&lt;p&gt;Let’s start with one of the most interesting authentication issues I’ve ever reported.&lt;/p&gt;
&lt;img src='https://miro.medium.com/v2/resize:fit:720/format:webp/1*McB2hI75sOM7gMXR3_zc7g.jpeg' alt='sss'&gt;
&lt;p&gt;So, let’s talk about the critical vulnerability I found in what we’ll call &lt;mark&gt;example.com&lt;/mark&gt;&lt;/p&gt;
&lt;p&gt;I started by testing the login functionality of the main application. Since I had only discovered the login page about 10 minutes earlier, I simply began interacting with it, clicking through the functionality and looking for anything interesting.&lt;/p&gt;</description></item></channel></rss>