<?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 Syntax Error on Medium]]></title>
        <description><![CDATA[Stories by Syntax Error on Medium]]></description>
        <link>https://medium.com/@SyntaxError4?source=rss-eb1c07a8a9c8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*OCeaGUvAu-uozhAUqhywkQ.jpeg</url>
            <title>Stories by Syntax Error on Medium</title>
            <link>https://medium.com/@SyntaxError4?source=rss-eb1c07a8a9c8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 21:30:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@SyntaxError4/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[Blind XSS for beginners]]></title>
            <link>https://infosecwriteups.com/blind-xss-for-beginners-c88e48083071?source=rss-eb1c07a8a9c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/c88e48083071</guid>
            <category><![CDATA[bugcrowd]]></category>
            <category><![CDATA[blind-xss]]></category>
            <category><![CDATA[xs]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[hackerone]]></category>
            <dc:creator><![CDATA[Syntax Error]]></dc:creator>
            <pubDate>Mon, 28 May 2018 02:11:33 GMT</pubDate>
            <atom:updated>2018-07-30T18:05:36.363Z</atom:updated>
            <content:encoded><![CDATA[<p>I get a lot of DM’s in twitter asking questions about Blind XSS like which tool to use, how to register in XSShunter, where to spray the payload etc etc.So I am writing this blog in hopes of answering some of those questions.<br><strong>Note</strong>: This article is for people who are just starting with bug bounty hunting.Leets can leave this blog right here:)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FGB0lKzzxIv1te%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FGB0lKzzxIv1te%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FGB0lKzzxIv1te%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="237" frameborder="0" scrolling="no"><a href="https://medium.com/media/bc1905bd90ca6cf2dcf7c98a3f4f1f76/href">https://medium.com/media/bc1905bd90ca6cf2dcf7c98a3f4f1f76/href</a></iframe><p><strong>What is Blind XSS?</strong></p><p>It is a type of stored XSS where attackers input is saved by server and is reflected in a totally different application used by system admin/team member.</p><p><strong>Tools you can use for Blind XSS:</strong></p><p>Currently I use the web version of <a href="https://xsshunter.com/features">XSShunter</a> for finding Blind XSS.There are few other tools which you can use:</p><ul><li><a href="https://github.com/ssl/ezXSS"><strong>ezXSS</strong></a>(has 2FA, email reports, share reports feature)</li><li><a href="https://github.com/LewisArdern/bXSS"><strong>bXSS</strong></a>(Has slack/sms notification feature)</li><li><a href="https://knoxss.me/?page_id=2"><strong>KNOXSS</strong></a>(has email feature)</li><li><strong>Burp Collaborator</strong></li></ul><p><strong>How to register for XSShunter? Is it free? Do we need a domain in our name to use XSShunter?</strong></p><p>I use the web version of XSShunter as I don’t have patience to setup the tool on my server:) Its free of cost and you can set it up by visiting <a href="https://xsshunter.com/signup">XSShunter</a> website .Enter all the mandatory fields, in the Custom Subdomain text box you can enter any 2–3 characters.(<strong><em>You are not supposed to enter your website URL here</em>:)</strong>).With that you should be set to use the tool.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rwRDW98NlOVl1YIRrtYeQg.png" /></figure><p>You can setup XSSHunter on your server by following these <a href="https://github.com/mandatoryprogrammer/xsshunter">instructions</a></p><p>I also use the <a href="https://knoxss.me/">KNOXSS</a> firefox plugin sometimes.If knoxss finds Blind XSS in a website it will mail you the vulnerability details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/826/1*QxrbeUzXGtXZzHrF18DCvg.png" /></figure><p><strong>So where do you get the payloads from and where do you spray the payloads?</strong></p><p>Within XSShunter there is a tab for payloads,You can get all the payloads from there and its better to have a copy of all the payloads locally with you so that you can use/spray it when you need it.</p><p>Now moving to questions about where to spray these payloads, this has been discussed on twitter/slack a lot of times.Here are few tips from top BB hunters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LDDgcc1MT8ryZhefchJ0_w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/922/1*zwWGlSP4PQJ8js6lAk6NOQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/1*KiQx2UsulkC0CP9v3zVjbQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GzAsx6KjyuWZjcrOVNgQlw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Oywdbri_JnmaogzUXiw9g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BK--JxAEIC4cOMOp_InSrg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*21_GL0rCzvm6JYqOsGw4LQ.png" /></figure><p><strong>Any interesting BXSS which I have found?</strong></p><ul><li>In a private bounty site, there was an option to create reports.I created a new report with report name as blind XSS payload.For my Luck, the company had a daily batch job which would sync the data across all their QA/Stage and pentest environments. Next day my XSShunter portal was full of reports with payload firing in 6–7 different internal environments owned by customer .Company Paid 5000$ for BXSS in 6 different endpoints.</li><li>Submitted Blind XSS payload in <strong>contact me</strong> form in PBB program and it fired in their backend salesforce application.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/608/1*94amiHswmkXFZtvONI6QfA.png" /></figure><ul><li>Submitted Blind XSS payload in a chat request and it fired in marketo application which company was using to collect chat data.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/979/1*jeCXqrZVjGzdXtHH2_CQ-g.png" /></figure><p><strong>Any other writeups/tutorials to refer?</strong></p><ul><li><a href="https://thehackerblog.com/breaching-a-ca-blind-cross-site-scripting-bxss-in-the-geotrust-ssl-operations-panel-using-xss-hunter/index.html">https://thehackerblog.com/breaching-a-ca-blind-cross-site-scripting-bxss-in-the-geotrust-ssl-operations-panel-using-xss-hunter/index.html</a></li><li><a href="https://mhmdiaa.github.io/blind-xss-in-spotify/">https://mhmdiaa.github.io/blind-xss-in-spotify/</a></li><li><a href="https://hackerone.com/reports/275518">https://hackerone.com/reports/275518</a></li><li><a href="https://hackerone.com/reports/314126">https://hackerone.com/reports/314126</a></li><li><a href="https://brutelogic.com.br/blog/blind-xss-code/">https://brutelogic.com.br/blog/blind-xss-code/</a></li><li><a href="http://www.agarri.fr/kom/archives/2017/04/04/exploiting_a_blind_xss_using_burp_suite/index.html">http://www.agarri.fr/kom/archives/2017/04/04/exploiting_a_blind_xss_using_burp_suite/index.html</a></li><li><a href="https://thehackerblog.com/poisoning-the-well-compromising-godaddy-customer-support-with-blind-xss/">https://thehackerblog.com/poisoning-the-well-compromising-godaddy-customer-support-with-blind-xss/</a></li></ul><p><strong>Update(30/07/2018)</strong></p><p>Many of you had question about how to check if XSShunter is working fine or not.Simple!</p><p>Take all the payloads from the XSShunter site and save it into a HTML file and open that html file in your browser.After file has opened,go to XSShunter and check if you see any new entries.If there are entries then XSShunter is working fine.</p><p>For any questions, you can get in touch with me at <a href="https://twitter.com/SYNTAXERRORBA">Syntaxerror</a></p><p>until next time</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fg9582DNuQppxC%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fg9582DNuQppxC%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Fg9582DNuQppxC%2Fgiphy-downsized-large.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/0eba96b395f1e17a357fe179074ce870/href">https://medium.com/media/0eba96b395f1e17a357fe179074ce870/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c88e48083071" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/blind-xss-for-beginners-c88e48083071">Blind XSS for beginners</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>
        <item>
            <title><![CDATA[Reflective XSS and Open Redirect on Indeed.com subdomain]]></title>
            <link>https://medium.com/@SyntaxError4/reflective-xss-and-open-redirect-on-indeed-com-subdomain-b4ab40e40c83?source=rss-eb1c07a8a9c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4ab40e40c83</guid>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Syntax Error]]></dc:creator>
            <pubDate>Mon, 04 Sep 2017 15:23:05 GMT</pubDate>
            <atom:updated>2017-09-04T15:23:05.642Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi Again! So here is one more writeup on a simple bug I found on Indeed.com subdomain.</p><p>As always I looked up for subdomains using Sublist3r tool.</p><p>While I was browsing through <a href="http://offfers.indeed.com/">offfers.indeed.com</a> subdomain ,I noticed a functionality where a user could choose some filters from dropdown and create a PDF report of the data which was generated.</p><p>I quickly selected some values and generated the report.When I Opened the Report<strong> </strong>,I noticed that the URL had an extra parameter <strong>Target</strong> which had the file location for the PDF file.</p><p><a href="http://offers.indeed.com/directcontent.html?target=http://offers.indeed.com/company/syncdata.pdf">http://offers.indeed.com/directcontent.html?target=http://offers.indeed.com/company/xy/xxyy.pdf</a></p><p>On seeing <strong>Target</strong> parameter in URL, my instant thought was to test for Open redirect .So I entered Target parameter value as <a href="https://google.com/">https://www.google.com</a> and I noticed it was actually taking user to Google.com</p><p><strong>Vulnerable URL</strong> :http://offers.indeed.com/directcontent.html?target=http://www.google.com</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcontent.screencast.com%2Fusers%2Fbaiju1988%2Ffolders%2FJing%2Fmedia%2Fe916d365-91c9-4aaf-b45d-58900c5f4a20%2Fjingswfplayer.swf&amp;fv=thumb%3Dhttps%3A%2F%2Fcontent.screencast.com%2Fusers%2Fbaiju1988%2Ffolders%2FJing%2Fmedia%2Fe916d365-91c9-4aaf-b45d-58900c5f4a20%2FFirstFrame.jpg%26containerwidth%3D1279%26containerheight%3D646%26content%3Dhttps%3A%2F%2Fcontent.screencast.com%2Fusers%2Fbaiju1988%2Ffolders%2FJing%2Fmedia%2Fe916d365-91c9-4aaf-b45d-58900c5f4a20%2F00000289.swf%26blurover%3Dfalse&amp;url=https%3A%2F%2Fcontent.screencast.com%2Fusers%2Fbaiju1988%2Ffolders%2FJing%2Fmedia%2Fe916d365-91c9-4aaf-b45d-58900c5f4a20%2F00000289.swf&amp;image=https%3A%2F%2Fthumb.screencast.com%2F3%2Fe916d365-91c9-4aaf-b45d-58900c5f4a20%2Fthumb.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=application%2Fx-shockwave-flash&amp;schema=screencast" width="1279" height="646" frameborder="0" scrolling="no"><a href="https://medium.com/media/3a3acd171b06a04b0410c0117e8ac034/href">https://medium.com/media/3a3acd171b06a04b0410c0117e8ac034/href</a></iframe><p>Next was to check if the same parameter was vulnerable to XSS as well. I gave the <strong>Target</strong> parameter value as <strong>javascript:alert(1)</strong> and as I was suspecting alert box popped up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0d7t3dy77biMtJxFUmKuyw.png" /></figure><p>I reported this issue to Indeed Via Bugcrowd and the bug was resolved within a week.As part of fix, they completely removed this functionality from the site.</p><p>For any question,You can get in touch with me <a href="https://twitter.com/SYNTAXERRORBA">@syntaxerror</a></p><p>Untill next time</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*EVbICsvHdXSk_6UksL1D9A.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4ab40e40c83" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I found Reflective XSS in Yahoo Subdomain]]></title>
            <link>https://medium.com/@SyntaxError4/how-i-found-reflective-xss-in-yahoo-subdomain-3ad4831b386e?source=rss-eb1c07a8a9c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ad4831b386e</guid>
            <category><![CDATA[yahoo]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[xs]]></category>
            <category><![CDATA[reflectivexss]]></category>
            <dc:creator><![CDATA[Syntax Error]]></dc:creator>
            <pubDate>Sun, 03 Sep 2017 18:41:12 GMT</pubDate>
            <atom:updated>2017-09-03T18:41:12.193Z</atom:updated>
            <content:encoded><![CDATA[<p>When 2017 started,I had a bounty goal of finding a bug in Yahoo but I never actually got time to look into their program. One day I planned to go for it.So here is the writeup on how I found Reflective XSS on a yahoo subdomain. This is my first writeup so please ignore any mistakes that you find.</p><p>First step was to find subdomains on yahoo and the tool I used was <a href="https://github.com/aboul3la/Sublist3r"><em>Sublist3r</em></a>(<a href="https://github.com/aboul3la/Sublist3r">https://github.com/aboul3la/Sublist3r</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*V5k7BJLMSP6fhpWFitdpVQ.gif" /></figure><p>Once I had the list,I started checking the subdomains one by one.During that time my attention went to one of the subdomains: <a href="https://hkfood.yahoo.com/">https://hkfood.yahoo.com</a></p><p>There was a search bar on the site to lookup for recipes and I initially tried couple of payloads to see what characters were filtered.For my luck, my inital payload itself worked and I could pop XSS</p><p><strong>Vulnerable URL :</strong> <a href="http://hkfood.yahoo.com/search_result#keywords=%E2%80%9C/&gt;.&lt;&lt;img%20src=x%20onerror=alert(1)//%E2%80%9D&amp;gt;&gt;&amp;lt;&amp;gt;&amp;page=1">http://hkfood.yahoo.com/search_result#keywords=“/&gt;.&lt;&lt;img src=x onerror=alert(1)//”&amp;gt;&gt;&amp;lt;&amp;gt;&amp;page=1</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HSUatZ5W_h-Ypzh-P3c7wA.png" /></figure><p>I reported the bug to Yahoo and the bug was Resolved the very next day.I rechecked the Vulnerable URL and was not able to reproduce the issue.</p><p>After 2 days,I was getting Bored and thought about retesting around the same XSS bug.This time I found that &lt;script&gt;&lt;img&gt; tags were being filtered.</p><p>So I started trying different combination of payloads to see if I can break the URL. To get &lt;script&gt; tag working,I broke it in pieces like below and added that to the old vulnerable URL and Hurray!!!</p><p><strong>Payload: &lt;scr&lt;script&gt;ipt&gt;alert(1)&lt;/scr&lt;/script&gt;ipt&gt;</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*OBJist0ZJaNrp2rQO4AdJA.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zn4PLdD_IsRiule24LDWCw.png" /></figure><p><strong>Tips:</strong></p><ul><li>Always Retest your bugs after its marked Resolved.There is a good chance that you will find a bypass.</li><li>I have seen some folks using tools/scripts to get sublist3r output in hyperlinks format.You can simply copy sublist3r output, paste it in gmail and mail it to yourself to get the output URL’s as hyperlinks.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/312/1*IWHP_gq3-aIvI2DWmvtH1g.png" /></figure><p>Thanks for taking time to read my blog. For any questions, you can get in touch with me at <a href="https://twitter.com/SYNTAXERRORBA">Syntaxerror</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ad4831b386e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>