<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by file.bug on Medium]]></title>
        <description><![CDATA[Stories by file.bug on Medium]]></description>
        <link>https://medium.com/@file_d0t_bug?source=rss-0dfeda3084bd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*m2o0C0DGUhztgyVYVeegaQ.png</url>
            <title>Stories by file.bug on Medium</title>
            <link>https://medium.com/@file_d0t_bug?source=rss-0dfeda3084bd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:26:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@file_d0t_bug/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Reflected XSS — Part 2]]></title>
            <link>https://medium.com/@file_d0t_bug/reflected-xss-part-2-0a0b2cb0a314?source=rss-0dfeda3084bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/0a0b2cb0a314</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <dc:creator><![CDATA[file.bug]]></dc:creator>
            <pubDate>Wed, 01 Oct 2025 19:18:59 GMT</pubDate>
            <atom:updated>2025-10-01T19:18:59.255Z</atom:updated>
            <content:encoded><![CDATA[<h4>بسم الله الرحمن الرحيم و الصلاة و السلام على أشرف الأنبياء و المرسلين</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2d5WPPSqEP6VDki-KTm4kw.jpeg" /></figure><p><strong>Introduction 📝</strong></p><p>Hey I am Ruba Khaled <em>(file.bug)</em> ,I found a <strong>reflected XSS</strong> in a public bug bounty program inside a password-reset page. <br> This is part 2 of my XSS journey — read part 1 here:</p><p><a href="https://medium.com/@file_d0t_bug/they-said-xss-was-dead-then-i-got-paid-my-first-bounty-in-2025-6eb8d27c6c1a">They Said XSS Was Dead… Then I Got Paid 💸 (My First Bounty in 2025)</a></p><p><strong>Recon tip — subdomain enumeration 🕵️‍♀️</strong></p><p>Before diving in: for subdomain enumeration I often use this website because it returns unique results that some scanners and Google dorks miss:</p><p><a href="https://subdomainfinder.c99.nl/">Visit Here</a></p><p><strong>How I discover Reflected xss bug? Any tool ? ⚒️</strong></p><p>I prefer manual hunting over blindly running tools. I test each parameter manually, and only when I can’t find anything I run a parameter-fuzzing tool. One tool I use is <strong>Arjun</strong> (I run it with the default wordlist):</p><pre>arjun -u http://example.com</pre><p>for Installation details 📥:</p><p><a href="https://github.com/s0md3v/Arjun">GitHub - s0md3v/Arjun: HTTP parameter discovery suite.</a></p><p><strong>The bug 🐞</strong></p><p>I’ll call the target <em>target.com</em> because the issue is still open.</p><p>While testing <em>target.com</em>, I checked the password reset flow. I entered my email and received the usual password-reset email:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/381/1*DoVUgwoOE9Q8AFwq2H8iAQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/479/1*eDkQntyQ1D8QjMJ4vNxwWQ.jpeg" /><figcaption>There is some parameters, let test Rxss</figcaption></figure><p>I followed the link and inspected the page source.</p><p><strong>Token parameter 🔐</strong></p><p>I changed the token value to see whether it was reflected in the page source. It was reflected inside an HTML attribute, but only alphabetical characters appeared; the double quote &quot; (which would close the attribute value) was blocked.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/739/1*hnkcdt6QSt_VSvqdjbzqCA.jpeg" /><figcaption>token reflection in source</figcaption></figure><p><strong>Email parameter 📧</strong></p><p>Next I checked the email parameter. My email is also reflected in the page source.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/651/1*0i7fm-uyT1-xeDufb6pVEQ.jpeg" /><figcaption>email reflected in source</figcaption></figure><p>I tested injecting a value with a quote:</p><p>jjjjjjjjj&quot;</p><p>The double quote &quot; was <strong>reflected successfully</strong> inside a &lt;script&gt; tag.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/509/1*b92XTlTPusAt_gQro9rX_g.png" /></figure><p>Since the injection point was inside a &lt;script&gt; block, I didn’t need to inject a new &lt;script&gt; tag — I could close strings and break the existing JavaScript context.</p><p><strong>Payload and How it works 🧩</strong></p><p>I used this simple payload:</p><pre>&quot;);alert(&#39;XSS&#39;)// </pre><p>How it works:</p><p>• &quot;) — closes the open string and the open parenthesis in the existing JS.</p><p>• ; — ends the current statement.</p><p>• alert(&#39;XSS&#39;) — shows a popup to demonstrate code execution (you can run any JS).</p><p>• // — comments out the rest of the original line to avoid syntax errors.</p><p>Because the email parameter was inserted directly into a script block without proper encoding, the payload executed successfully.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/551/1*Qz_F2MxYRJv-p83HKpMLSQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*GIXgo3apVo6yFk1pKvOb3A.jpeg" /></figure><p><strong>The end 🎬</strong></p><p>Thanks for reading! If you enjoyed this, please clap 👏🏼👏🏼👏🏼 and follow for more bug-bounty write-ups — maybe there will be a Part 3 of my XSS journey !</p><p>Contact: <a href="https://x.com/file_d0t_bug">file_d0t_bug</a> on X (Twitter) 🐦</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0a0b2cb0a314" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Found: an IDOR in a Game Full of Hunters ]]></title>
            <link>https://medium.com/@file_d0t_bug/found-an-idor-in-a-game-full-of-hunters-0ee8abd08589?source=rss-0dfeda3084bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/0ee8abd08589</guid>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <dc:creator><![CDATA[file.bug]]></dc:creator>
            <pubDate>Thu, 25 Sep 2025 07:24:49 GMT</pubDate>
            <atom:updated>2025-09-29T17:21:50.922Z</atom:updated>
            <content:encoded><![CDATA[<p>Found: an IDOR in a Game Full of Hunters 👀</p><h4>اللهم علمنا ما ينفعنا، وانفعنا بما علمتنا، وزدنا علما &quot;سُبْحَانَكَ لا عِلْمَ لَنَا إِلَّا مَا عَلَّمْتَنَا إِنَّكَ أَنْتَ الْعَلِيمُ الْحَكِيمُ&quot;.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aaK3oxslnc9jF1X5d_PTow.png" /></figure><p><strong>Introduction 👋</strong></p><p>Hi — I’m <em>file.bug</em>. Today I’ll show how I discovered a simple <strong>IDOR</strong> on a game that allowed me to join private groups. Let’s dive in.</p><p><strong>What is an IDOR ❓</strong></p><p>An <strong>IDOR (Insecure Direct Object Reference)</strong> is a type of broken access control where an application allows an attacker to bypass authorization by directly accessing objects (like user records or files) using user-supplied identifiers in URLs or requests. This happens when the app fails to verify whether the requesting user has permission to access the specified object, which can lead to unauthorized viewing or modification of data.</p><p>If you want to learn more, PortSwigger Academy has a great guide on <a href="https://portswigger.net/web-security/access-control/idor">IDOR</a>.</p><p><strong>The bug 🐞</strong></p><p>To avoid disclosing the game before the issue is resolved, I’ll call it <strong>gameTarget.com</strong> . In this write-up I only interact with API endpoints — sharing UI details might reveal the game.</p><p>gameTarget.com allows players to create groups (either private with a password, or public that any player can join). When a player joins a group, their score is added to that group’s leaderboard.</p><p>While looking for groups to join <em>(In the search for groups functionality)</em>, I noticed an API endpoint that returns all game group IDs, names, whether they are public or private, and the admins for each group ID.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*clazgXcsGpd_hrJm7F-nPA.png" /></figure><p>On the &quot;View My Group&quot; page , There was another endpoint that, when called with a specific group ID in the URL, returned the group content (players’ team names, ratings, etc.) — <strong>and it returned the password too if the group was private.</strong> 😳</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZQnb3m0qYZTbK-cVEqpYHQ.jpeg" /><figcaption>It is my private group password</figcaption></figure><p><strong>My test case 🕵🏼‍♀️</strong></p><p>I created a private group called <em>The_secret_team</em> with an unusual password, then I intentionally forgot the password and left the group.</p><p>Using the endpoint that lists all groups, I found the group’s ID: <strong>12089.</strong> I then called the endpoint that returns the group password — and it returned the password.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/988/1*VLLLHCLOzPA7-077L3eQEA.jpeg" /></figure><p>I used that password to join the group successfully !</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*zWvhJ6wa-LJyltPJqhP_gg.jpeg" /></figure><p>After that, I tried to access other players’ private teams without joining them. Bug hunter here are more than normal players 🤣.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/455/1*4bkN5qPBl0nwGOpfekMXKA.png" /><figcaption>Oh , SQLi and XSS payloads flying everywhere 😭</figcaption></figure><p><strong>The report 📝</strong></p><p>Should I report this? 🤔 I worried it might be a duplicate because many hackers were active in the same area, and the issue seemed low severity (there&#39;s no direct interaction between players — only a leaderboard that shows ranking). I asked a few people on Discord and they encouraged me to report it. 👍</p><p>I submitted the report — and it was accepted and paid. 😎💰</p><p><strong>Wrap-Up 🎬</strong></p><p>Thanks for reading! If you enjoyed this, please clap 👏🏼 and follow me for more bug bounty write-ups.</p><p>Have a question or want to connect? DM me on X (Twitter) :<br>👉 <a href="https://x.com/file_d0t_bug">file_d0t_bug</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0ee8abd08589" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[They Said XSS Was Dead… Then I Got Paid  (My First Bounty in 2025)]]></title>
            <link>https://medium.com/@file_d0t_bug/they-said-xss-was-dead-then-i-got-paid-my-first-bounty-in-2025-6eb8d27c6c1a?source=rss-0dfeda3084bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/6eb8d27c6c1a</guid>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <dc:creator><![CDATA[file.bug]]></dc:creator>
            <pubDate>Wed, 10 Sep 2025 16:52:53 GMT</pubDate>
            <atom:updated>2025-09-10T17:07:19.047Z</atom:updated>
            <content:encoded><![CDATA[<h4>بسم الله الرحمن الرحيم و الصلاة و السلام على أشرف الأنبياء و المرسلين</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*55ryEV9slwD0_kET" /></figure><p><strong>About Me</strong></p><p>Hi, my name is Ruba Khaled a.k.a. (file.bug) 🐞💻.</p><p>I’m a beginner bug bounty hunter and an Electrical &amp; Electronic Engineering student ⚡🔌.</p><p>Last month, I discovered my third valid bug but this time… I actually got my first bounty 💰!<br>So grab some coffee and let’s dive in.</p><p><strong>XSS? 🤔</strong></p><p>If you’re new to bug hunting, you might wonder: <em>“What’s this XSS thing everyone keeps talking about?”</em></p><p>Well, <strong>Cross-Site Scripting (XSS)</strong> is basically an injection bug that allows attackers to run malicious JavaScript on a legitimate site. 🕵️‍♂️💻</p><p>It has three categories:</p><p>• 🍭 Reflected XSS (Rxss)</p><p>• 🛒 Stored XSS (Sxss)</p><p>• 🏠 DOM-based XSS</p><p>If you want to go deeper, I recommend checking out <a href="https://portswigger.net/web-security/cross-site-scripting">PortSwigger Academy</a> — it’s a great resource for learning about bugs.✨</p><p>In this write-up, I’ll share how I found a Reflected XSS in a public bug bounty program.</p><p><strong>The Bug Story 🕵️‍♀️</strong></p><p>⚠️ First things first: this bug isn’t patched yet, so for safety I’ll use target.com as a placeholder.</p><p>I was testing a social networking site (target.com). At first, it looked squeaky clean… no bugs, no issues. So I was like: <em>“Okay, nothing here. Let’s log out and move on.”</em></p><p>But “<em>Wait… what about the login page? 👀”</em></p><p>So, I started digging into the page source and noticed some hidden input fields.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/1*L3x47YuSwRR6vryrv8yPDA.jpeg" /></figure><p>I tried changing their values like this:</p><pre>https://target.com/login?option=mm&amp;view=mm&amp;op2=mm&amp;return=mm&amp;message=mm&amp;loginfrom=mm </pre><p>Only the <strong>return</strong> parameter actually changed things. Turns out it was taking a redirect URL (encoded in Base64) after login.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/503/1*MileUfgJkvcQPFc8FbbC6w.png" /></figure><p><strong>Let’s Test for XSS 🧪</strong></p><p>I injected a &quot;, and… it was successfully reflected!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HYIQh2nk6TChL_QTvO8m4w.jpeg" /></figure><p>So I tried this:</p><pre>mm&quot;&gt;&lt;img src=&quot;x&quot; onerror=&quot;alert()&quot;&gt; <br></pre><p>But… 💔 WAF (Web Application Firewall) stripped everything between &lt; and &gt;.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gvB2MTuBVQK0ELAhDAHgOg.jpeg" /></figure><p>Think… Think… Think… 🤔</p><p>I opened my XSS notes ,And then I found this payload:</p><pre>&quot; accesskey=&quot;x&quot; onclick=&quot;alert(’message_here’) </pre><p>💡 <em>How it works:</em></p><p>• The first &quot; closes the attribute.</p><p>• Then I sneak in an accesskey=&quot;x&quot; (which lets you trigger it with a keyboard shortcut).</p><p>• Finally, the onclick event runs when the accesskey is pressed.</p><p>So on <strong>Firefox</strong>, when the victim presses Alt + Shift + X…Alert box pops up!</p><p>(Other browsers need different shortcuts; you can find the full list on Wikipedia)</p><p>👉 Full list of access keys: <a href="https://en.m.wikipedia.org/wiki/Access_key">Wikipedia Accesskey</a></p><p><strong>And the Result? 🏆</strong></p><p>It is successfully injected!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lBjMfpO9EYFfOf4ZFhUrbA.jpeg" /></figure><p>Triggered alert box 🎉</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*YeXlWedQ202ya_Tba2w3yw.jpeg" /></figure><p>And that’s how I earned my <strong>first ever bounty!</strong> 😎💰</p><p><strong>Wrap-Up</strong> 🎬</p><p>Thanks for reading! If you enjoyed this, don’t forget to 👏🏼 clap (maybe more than once 👏🏼👏🏼👏🏼) and follow me for more bug bounty write-ups.</p><p>Got questions or just want to connect? DM me on X (Twitter):<br>👉 <a href="https://x.com/file_d0t_bug">file_d0t_bug</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6eb8d27c6c1a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>