<?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 Shrirang Diwakar on Medium]]></title>
        <description><![CDATA[Stories by Shrirang Diwakar on Medium]]></description>
        <link>https://medium.com/@shrirangdiwakar?source=rss-c8599346ffe6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*LINZ2fv_Lk2Y3JU_SkTu5A.jpeg</url>
            <title>Stories by Shrirang Diwakar on Medium</title>
            <link>https://medium.com/@shrirangdiwakar?source=rss-c8599346ffe6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 21:50:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shrirangdiwakar/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[Bypassing 403s like a PRO! ($2,100): Broken Access control]]></title>
            <link>https://shrirangdiwakar.medium.com/bypassing-403s-like-a-pro-2-100-broken-access-control-66beef4afa8c?source=rss-c8599346ffe6------2</link>
            <guid isPermaLink="false">https://medium.com/p/66beef4afa8c</guid>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[broken-access-control]]></category>
            <dc:creator><![CDATA[Shrirang Diwakar]]></dc:creator>
            <pubDate>Fri, 21 Apr 2023 13:18:51 GMT</pubDate>
            <atom:updated>2023-04-21T13:18:51.227Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello hunters, hope you’re doing well, and apologies for the huge gap in posting articles.</p><p>This article highlights my way of dealing with 403s and how I managed to get a P1 in minutes!😍</p><p>Excited to share this story with you all. Let’s get started!😁</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*nca2S7WsgrZp1wK5eYtlSQ.jpeg" /></figure><h4><strong>Let&#39;s Begin</strong></h4><p>A Broken access control vulnerability is a type of security flaw that allows an unauthorized user access to restricted resources. By exploiting this vulnerability, attackers can circumvent standard security procedures and gain unauthorized access to sensitive information or systems.</p><p>You might have observed that for sensitive endpoints such as .htaccess, config.php, etc., the server usually returns a <em>403 forbidden</em> response. But what does that mean?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/304/1*p4dL3t13CjEQlaqS7cZ1AQ.jpeg" /></figure><p>According to the Mozilla documentation, The HTTP 403 Forbidden response status code indicates that <strong>the server understands the request but refuses to authorize it.</strong></p><p><strong><em>BUT, If the access control mechanism applied is weak, an attacker can bypass the security controls and access the restricted resource</em></strong></p><h4><strong>About the application:</strong></h4><p>The Web application is an IOT service delivery platform and offers a variety of IOT-related services. As usual, I begin my directory enumeration with the dirbuster wordlists and find a /console endpoint which returns a 403 response.</p><p>The <strong>/console</strong> endpoint is our further lead. Let’s move ahead with the bypass techniques.</p><h4><strong>Ways to bypass 403 endpoints:</strong></h4><p>Bypassing 403 includes multiple ways such as HTTP verbs/methods fuzzing, HTTP headers fuzzing, Path fuzzing, etc. However, we will focus on the path fuzzing technique.</p><h4>Path fuzzing:</h4><p>If <em>/path</em> is blocked:</p><p><strong>Try using . or %2e: </strong><em>/</em>%2e/path <strong><br></strong><em>(if the access is blocked by a proxy, this could bypass the protection). Try also /%252e/path (double URL encode)</em></p><p><strong>Try Unicode bypass:</strong> <em>/%ef%bc%8fpath</em> <br><em>(The URL encoded chars are like “/”) so when encoded back it will be //path and maybe you will have already bypassed the /path name check</em></p><p><strong>Other path bypasses</strong>:</p><p>site.com/secret –&gt; HTTP 403 Forbidden<br>site.com/SECRET –&gt; HTTP 200 OK<br>site.com/secret/ –&gt; HTTP 200 OK<br>site.com/secret/. –&gt; HTTP 200 OK<br>site.com//secret// –&gt; HTTP 200 OK<br>site.com/./secret/.. –&gt; HTTP 200 OK<br>site.com/;/secret –&gt; HTTP 200 OK<br>site.com/.;/secret –&gt; HTTP 200 OK<br>site.com//;//secret –&gt; HTTP 200 OK<br>site.com/secret.json –&gt; HTTP 200 OK (ruby)</p><p>I prefer using the <a href="https://portswigger.net/bappstore/444407b96d9c4de0adb7aed89e826122">403 Bypasser Burp extension</a> by Gil Nothmann to automate the bypass techniques.</p><h4>What worked for me?</h4><p>Using Burp, I captured the GET request to the <strong>/console</strong> endpoint and sent the request to the 403 Bypasser burp extension. The extension worked like a charm and provided me with the results.</p><p><strong><em>Usage of a . (dot) or %2e in the URL path (/%2e/console) allowed me to bypass the access control check and gave me access to the Internal system console manager.</em></strong></p><p>I quickly added rules in Burp to prepend every necessary request with /%2e/ so that I can browse through the console manager conveniently.</p><p>The console manager revealed very sensitive component data including build details, OS details, and user details, and also provided a CLI component for code execution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/522/1*WCQDJye8HjN3SPRaB8r66Q.jpeg" /></figure><h4>Conclusion:</h4><p>The submission was triaged quickly and categorized as a P1. I was later rewarded with a <strong>$2,100 bounty.</strong></p><p>That’s all for this article, I hope you guys enjoyed this form of learning ❤</p><p>Stay Safe 🤗</p><p>Follow my Instagram Creator account for more Bug Bounty &amp; Ethical Hacking related content: <a href="https://www.instagram.com/shrirangdiwakar/">https://www.instagram.com/shrirangdiwakar/</a> 😇</p><p>My LinkedIn: <a href="http://www.linkedin.com/in/shrirangdiwakar">www.linkedin.com/in/shrirangdiwakar</a> 🥰</p><p>Shower your love with the claps &amp; share this with your friends ❣</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66beef4afa8c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How a simple “Hey!” can turn into your worst Nightmare: Stored XSS]]></title>
            <link>https://shrirangdiwakar.medium.com/how-a-simple-hey-can-turn-into-your-worst-nightmare-stored-xss-d5a02b136506?source=rss-c8599346ffe6------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5a02b136506</guid>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Shrirang Diwakar]]></dc:creator>
            <pubDate>Sun, 01 Aug 2021 04:41:26 GMT</pubDate>
            <atom:updated>2021-08-01T04:49:43.689Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello Hunters, Hope you’re doing well. Ever thought about what can happen if you read any stranger’s “Hey!” message? Nothing will happen, right?! 🤔</p><p>Let me prove you wrong!! So relax and let me explain how a simple “Hey!” can turn into your worst nightmare!! 👻</p><p>I’m sure this would be you right now…😂</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*in8oIMyyDF2bHw8ekjZJZg.jpeg" /></figure><h3>Let’s Begin</h3><p>Cross-site scripting (XSS) is a common attack vector that injects malicious code into a vulnerable web application. Stored XSS is the most dangerous of all. To successfully execute a stored XSS attack, a perpetrator has to locate a vulnerability in a web application and then inject a malicious script into its server.<br>Unlike Reflected, The attacker does not need to find an external way of inducing other users to make a particular request containing their exploit. Rather, the attacker places their exploit into the application itself and simply waits for users to encounter it.</p><h3>Summary:</h3><p>The Web application is a global provider of cloud communications and allows devices to be connected anywhere and on any device through voice, video, and team messaging. So the application is vulnerable to a Stored Cross-Site Scripting (XSS) Vulnerability which allowed an attacker to execute his malicious Javascript code on the victim’s device, as soon as the victim interacts with the attacker in any way. (eg.message, task, etc)</p><p><strong>The Reason for the javascript execution was the “Last Name” parameter. </strong>Whenever you receive any message from a stranger/known person, some details which are visible include First Name, Last Name, Username, etc.<strong> </strong>In this scenario, the script was injected in the “Last Name” of the attacker,<strong> and</strong> <strong>the exploitation point was not sanitized properly after fetching the attacker’s Last Name. This allowed any Javascript code injected into “Last Name” to be executed on the Victim’s device.</strong></p><h3>Steps Followed:</h3><ol><li>Go to Edit Profile Section and inject the XSS payload given below in the “Last Name” field</li><li>Now Create a task with Assignee marked as “Self”</li><li>Send the task to the Victim with a simple “Hey!” message</li><li>As soon as, the victim reads your message/task, the script will get executed.</li></ol><p><strong>Payload:</strong> ”&gt;&lt;img src=z onerror=”alert(document.cookie)”</p><p>Scary, Isn’t it? 🥶</p><p>Wait…Wait…Wait! It&#39;s not over yet!! 😁</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/413/1*B45i7AN5II6qRT-uBb04sg.jpeg" /></figure><p>Exploiting one victim at a time is boring, right? So let’s try to use the application’s other feature of creating “Teams”!!😍</p><p>So now, As an attacker, we will create a Team of all our Victims and send the message just once. And all those who read fall into our well-organized Trap!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XunDDpGabru14BSZVTslrw.jpeg" /></figure><p>But as usual, the Bugcrowd Triager marked it as a “Duplicate” -&gt; I asked for reassessment -&gt; Marked duplicate of another submission again -&gt; I asked for reassessment again -&gt; Triaged (P2) and rewarded $500 (could’ve been $2500 submission, but a Tier 4)</p><p>That’s all for this article, I hope you guys enjoyed this form of learning ❤</p><p>Stay Safe 🤗</p><p>Follow my Instagram Creator account for more Bug Bounty &amp; Ethical Hacking related content: <a href="https://www.instagram.com/shrirangdiwakar/">https://www.instagram.com/shrirangdiwakar/</a> 😇</p><p>My LinkedIn: <a href="http://www.linkedin.com/in/shrirangdiwakar">www.linkedin.com/in/shrirangdiwakar</a> 🥰</p><p>Shower your love with the claps &amp; share this with your friends ❣</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5a02b136506" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I turned 0000 into $600: Phone Verification Bypass]]></title>
            <link>https://shrirangdiwakar.medium.com/how-i-turned-0000-into-600-phone-verification-bypass-b1c0f6eb568e?source=rss-c8599346ffe6------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1c0f6eb568e</guid>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <dc:creator><![CDATA[Shrirang Diwakar]]></dc:creator>
            <pubDate>Thu, 20 May 2021 23:19:05 GMT</pubDate>
            <atom:updated>2021-05-20T23:19:05.196Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello Hunters, This is a Tale of how I decoded the Verification flow of a well-known web application &amp; bypassed the Phone Verification process because of the Initial code set at the Backend ❤</p><p>Damn Excited! Can’t wait to share this…😍</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dbg0v_z5YJBTnkMwiA7ZLw.jpeg" /></figure><h3><strong>Let’s Begin</strong></h3><p>The Web Application was a Server Hosting Management System with 24x7 support, Datacentre facilities, etc. After creating an account, a server of the user’s choice is hosted which means a Resource was being utilized. <strong>However, the Unnecessary creation of accounts could lead to excessive exploitation of available resources.</strong></p><p><strong>For which, a Phone verification mechanism was implemented where the user has to enter the 4 digit code which was told, on a call received on the entered mobile number. </strong>And only upon entering the correct code, the user had access to the functionalities offered.</p><p><strong>The Phone Verification mechanism looked like this,</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/1*S01S9FA2sYsJc4zfH7Emow.png" /><figcaption>Phone Verification mechanism</figcaption></figure><h3>Here is the catch,</h3><p>While testing, I had to create multiple accounts &amp; going through this process seemed hectic so I tried to bypass this. So I started forming test cases for the inputs (phone number, verification code). Out of many test cases formed, this was the one that had a strong logic :</p><p><strong>Test Case:</strong> <strong>As you can see, the “Verification code” input is already placed without entering the phone number.</strong> The normal flow should have been, asking for the phone number first &amp; then the verification code. But here, things seem different 🤷‍♀️</p><p><strong><em>So What if I enter any value in the “Verification Code” input box before entering the phone number and click on “Verify Code”?</em>🤔</strong></p><p><strong><em>What if the developer had set a variable at the backend that held some initial value before the user clicks on “Call me Now”?</em>😮</strong></p><p>Going with the test case, I tried 1234, 1111, 8421, etc. but none of them worked. <strong>However, for 0000 the account got verified successfully meaning that the Phone verification was bypassed.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/1*YJwTbwccOwkCrEfm0rDsuw.png" /><figcaption>Account Verified Successfully</figcaption></figure><h3>Steps Followed :</h3><ol><li>Create an account</li><li>A Phone verification mechanism was implemented and also the Verification Code was asked at the same time making it vulnerable to the test case. So without entering the Phone number, enter 0000 in the “Verification Code” input box.</li><li>Your Account will be verified successfully.</li></ol><p><strong>So my <em>What ifs</em> were correct which means that a variable was set at the backend that held an initial value 0000 before the user clicks on “Call me Now”!</strong></p><p><strong>Hence, the title: “How I turned 0000 into $600”</strong> 💯😎</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ZGdXg5CuyUFFpSFXkTWMvQ.jpeg" /></figure><p>The Submission was triaged and I got rewarded with a $600 bounty under the P3 category 😁</p><p>That’s all for this article, I hope you guys enjoyed this form of learning ❤</p><p>Stay Safe 🤗</p><p>Follow my Instagram Creator account for more Bug Bounty &amp; Ethical Hacking related content: <a href="https://www.instagram.com/shrirangdiwakar/">https://www.instagram.com/shrirangdiwakar/</a> 😇</p><p>My LinkedIn: <a href="http://www.linkedin.com/in/shrirangdiwakar">www.linkedin.com/in/shrirangdiwakar</a> 🥰</p><p>Shower your love with the claps &amp; share this with your friends ❣</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1c0f6eb568e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Encrypted Payload -> Decrypted Execution ($600) : Stored XSS]]></title>
            <link>https://shrirangdiwakar.medium.com/encrypted-payload-decrypted-execution-600-stored-xss-3e517cea8f13?source=rss-c8599346ffe6------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e517cea8f13</guid>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[infosec]]></category>
            <dc:creator><![CDATA[Shrirang Diwakar]]></dc:creator>
            <pubDate>Thu, 25 Mar 2021 00:49:39 GMT</pubDate>
            <atom:updated>2021-03-25T00:49:39.783Z</atom:updated>
            <content:encoded><![CDATA[<h3>Encrypted Payload -&gt; Decrypted Execution ($600) : Stored XSS</h3><p>Hello Hunters, This is a Tale of how I used an Application’s feature against itself to give rise to a Stored Cross Site Scripting Vulnerability. So relax and Enjoy the article ❤</p><p>Damn Excited to share this story…..😍</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/374/1*SEeCQQnVKcvEFM1PZGxDSg.jpeg" /></figure><h3><strong>Let’s Begin</strong></h3><p>Cross site scripting (XSS) is a common attack vector that injects malicious code into a vulnerable web application. Stored XSS are the most dangerous of all. To successfully execute a stored XSS attack, a perpetrator has to locate a vulnerability in a web application and then inject malicious script into its server.<br>Unlike Reflected, The attacker does not need to find an external way of inducing other users to make a particular request containing their exploit. Rather, the attacker places their exploit into the application itself and simply waits for users to encounter it.</p><h3>Summary :</h3><p>The Web Application was a Server Hosting Management System with 24x7 support, Datacentre facilities, etc. <strong>The Application had a</strong> <strong>feature to create Support tickets for technical Support, server hosting support, Billing support, etc.</strong> Admins, technical support team members along with the application’s support team were now involved in a conversation. Here, we can raise our questions which were resolved by the support, similar like a Chat feature.</p><p>If any sensitive information such as passwords needed to be sent, <strong>an</strong> <strong>Encryption feature was added where any member can encrypt the message and send as a reply to the support ticket, which when clicked was getting decrypted.</strong> So after analysing deeper, I figured out a way to use their own feature which encrypted my specially crafted payload &amp; when clicked got executed giving rise to a Stored Cross Site Scripting Vulnerability.</p><h3>Steps Followed :</h3><ol><li>Created a Support Ticket</li><li>Analysed the “Encrypt Message” feature and figured out that the Encrypted message was decrypted on click in a &lt;textarea&gt; tag</li><li>Also, the application didn’t allow alert, prompt or confirm functions but allowed Uppercased version of them</li><li>So, Crafted a special payload to first escape the tag, then input as uppercased “ALERT(1)” but processed as “alert(1)” due to specially crafted payload</li><li>Using the “Encrypt Message” feature, encrypted the payload &amp; sent as a reply to the support ticket.</li><li>So if anyone from the support team, technical team or admin, clicks on the message (obviously would) to check the original content, it would be decrypted &amp; the payload then got executed.</li><li>Now, all victims involved in the application were vulnerable to XSS on decrypting the message💯</li></ol><p><strong>Payload : </strong>&lt;/textarea&gt;&lt;img src=x onerror=”var pop=’ALERT(document.cookie);’; eval(pop.toLowerCase());”</p><p><strong>Hence, the title : Encrypted Payload -&gt; Decrypted Execution 💯😎</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/471/1*SkF7PLLLQjPkGlGN_MNL4A.jpeg" /></figure><p>The Submission was triaged and I got rewarded with a $600 bounty under P3 category because the affected actors were the Admins, Technical Support Team &amp; the backend support, but the act that the technical team must be added by the admin is what lowered the possible impact 😁</p><p>That’s all for this Article, I Hope you guys enjoyed this form of learning ❤</p><p>Stay Safe 🤗</p><p>Follow my Instagram Creator account for more Bug Bounty &amp; Ethical Hacking related content : <a href="https://www.instagram.com/shrirangdiwakar/">https://www.instagram.com/shrirangdiwakar/</a> 😇</p><p>My LinkedIn: <a href="http://www.linkedin.com/in/shrirangdiwakar">www.linkedin.com/in/shrirangdiwakar</a> 🥰</p><p>Shower your love with the claps &amp; share this with your friends ❣</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e517cea8f13" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My First 4 Digit Bounty Tragedy ($1125) : Stored XSS]]></title>
            <link>https://shrirangdiwakar.medium.com/my-first-4-digit-bounty-tragedy-1125-stored-xss-fb171f911df?source=rss-c8599346ffe6------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb171f911df</guid>
            <category><![CDATA[stored-xss]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[report]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Shrirang Diwakar]]></dc:creator>
            <pubDate>Wed, 06 Jan 2021 23:03:42 GMT</pubDate>
            <atom:updated>2021-03-24T22:42:05.787Z</atom:updated>
            <content:encoded><![CDATA[<h3>My First 4 Digit Bounty Tragedy ($1125) : Stored XSS</h3><p>Hello Hunters, This is my FIRST Medium Article covering the Story of my FIRST 4 Digit bounty which was FIRST marked as a Duplicate but later found out to be a Unique submission after a long span of 25 days and also got gifted with a PentesterLab Pro Subscription for 3 months.😎</p><p>I’m very much excited to share this story or so called a TRAGEDY, with you all guys! 😂</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*YjnlWsxfj76Cn1wEOfgnXQ.jpeg" /></figure><h3>Let’s Begin…</h3><p>Cross site scripting (XSS) is a common attack vector that injects malicious code into a vulnerable web application. Stored XSS are the most dangerous of all. To successfully execute a stored XSS attack, a perpetrator has to locate a vulnerability in a web application and then inject malicious script into its server.<br>Unlike Reflected, The attacker does not need to find an external way of inducing other users to make a particular request containing their exploit. Rather, the attacker places their exploit into the application itself and simply waits for users to encounter it.</p><h3>Summary:</h3><p>The Vulnerable Web Application was a Content Management System (CMS). The Web Application had a Login/Signup feature and “Username” was considered as a Unique parameter for all Users, i.e. No two users can have the same Username.</p><p>To summarize, The “Username” input field was the <strong>injection point</strong> for malicious script and the script <strong>exploitation/execution point</strong> was another endpoint which was publicly accessible to all Users.</p><h3>Steps Followed:</h3><ol><li>After Registering for the Web application, Head to the “Edit Profile” Section.</li><li>In the “Edit Profile” Section, there was a “Username” input field which wasn’t sanitized.</li><li>Injected a simple and everyone’s favorite payload as <strong>“&gt;&lt;script&gt;alert(1);&lt;/script&gt;</strong> in the “Username” field and Saved the Changes.</li><li>Reload the Page and a beautiful POP-UP appears confirming the execution of script.</li></ol><h3>WAIT A MINUTE…. ISN’T THIS A SELF XSS? 😳</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/459/1*V4V9VBcsJra0kWnhphxTEg.jpeg" /></figure><p>For now, YES</p><p>BUT…I was testing on a Staging environment. So, Bugcrowd Team then reproduced the finding on the Production Environment and confirmed that the script injected in the “Username” was executed at an Endpoint which was publicly accessible to any user. So, it was marked as a P2 with category as, Cross-Site Scripting (XSS) &gt; Stored &gt; Non-Privileged User to Anyone.</p><p>BUT A DUPLICATE!! 😭</p><h3>Sad, isn’t it? This is how I felt… 😪</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*7CcpQTtoSNQm1owJGfLktw.jpeg" /></figure><p>After a Few days, I got a mail from Bugcrowd saying that My Report was identified as a Great Quality Report and I was gifted a 3 month PentesterLab Pro subscription.😍</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/833/1*RMpDWg-OY7YIesHT4TrI7w.jpeg" /></figure><p>I was very much happy as my work was appreciated. It seemed that my efforts were paid off.💯</p><p><strong>Little did I know, there was a BIG Surprise ahead…💰</strong></p><p>After 25 days, I found out 2 more Stored XSS on “FirstName” &amp; “LastName” parameters. I submitted reports for both of them for the same, “Edit Profile” Section.</p><p>I didn’t realize that the scripts at “Username”, “FirstName” &amp; “LastName” can also be injected at Registration Endpoint.🤦‍♂️</p><p>So all 3 reports were on the same “Edit Profile” section Endpoint and as I had already submitted for “Edit Profile” section Endpoint, both “FirstName” &amp; “LastName” submissions should have been marked as “Not Applicable”.</p><p><strong>BUT THEY WERE NOT!</strong></p><p>The submission for XSS at “LastName” was marked a duplicate of “FirstName” XSS submission and this submission was forwarded to verify.</p><p>I was in a doubt that, “FirstName” XSS submission should have been marked as Not Applicable because I had already submitted “Username” XSS submission at the same “Edit Profile” section Endpoint, then why it was considered for verifying?</p><p>Then after revisiting my “Username” XSS submission, I realized that the submission was marked as a Duplicate of another “Username” XSS submission but at Registration Endpoint whereas my submission was for “Edit Profile” endpoint.😮</p><p>So I decided to trap up the triager to make him realize this mistake and commented on my “LastName” XSS submission with change in Injection Endpoint and updated the Endpoint to “Registration” Endpoint, to which the triager responded saying that Registration Endpoint was already reported by another researcher. Then I asked him that If a submission is reported for Registration Endpoint and most probably it is the “Username” XSS submission then why was my earlier submission marked as a duplicate when it had “Edit Profile” injection endpoint.</p><p>Later, He realized this mistake and updated my 1 month old “Username” XSS submission for which I was rewarded with my First 4 Digit Bounty ($1125).😍</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*rnx40jz6-HNL23_akIiGzw.jpeg" /></figure><p>To be honest, I am thankful to the triager for making this mistake else I wouldn’t be gifted with the PentesterLab Pro Subscription. 😂</p><p>That&#39;s all for my FIRST Article, I Hope you guys enjoyed this form of learning ❤</p><p>Stay Safe 🤗</p><p>My LinkedIn: <a href="http://www.linkedin.com/in/shrirangdiwakar">www.linkedin.com/in/shrirangdiwakar</a></p><p>Follow my Instagram Creator account for more Bug Bounty &amp; Ethical Hacking related content : <a href="https://www.instagram.com/shrirangdiwakar/">https://www.instagram.com/shrirangdiwakar/</a></p><p>Thanks <a href="https://medium.com/u/1e2b7c9182d3">Raj Kaste</a> &amp; Ankit Sharma for helping me out 😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb171f911df" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>