<?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 A…$egun (Root) on Medium]]></title>
        <description><![CDATA[Stories by A…$egun (Root) on Medium]]></description>
        <link>https://medium.com/@A_Segun?source=rss-5993a2e04531------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*LdC-_XFUzNt7qCy5WX068w@2x.jpeg</url>
            <title>Stories by A…$egun (Root) on Medium</title>
            <link>https://medium.com/@A_Segun?source=rss-5993a2e04531------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:51:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@A_Segun/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[My First Critical Bounty: How I Went From robots.txt to Full Admin Access.]]></title>
            <link>https://medium.com/@A_Segun/my-first-critical-bounty-how-i-went-from-robots-txt-to-full-admin-access-322ae07f1247?source=rss-5993a2e04531------2</link>
            <guid isPermaLink="false">https://medium.com/p/322ae07f1247</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[freelancing]]></category>
            <category><![CDATA[web-security]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[A…$egun (Root)]]></dc:creator>
            <pubDate>Fri, 09 Jan 2026 19:34:23 GMT</pubDate>
            <atom:updated>2026-01-20T10:56:59.978Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>My First Critical Bounty: How I Went From robots.txt to Full Admin Access.</strong></p><p>Six months ago, I decided to learn cybersecurity. I chose bug hunting. I spent nights reading, doing labs, and hitting dead ends on real targets. Then I found this. It’s the story of how one weird line in a robots.txt file turned into a critical bug report and my first bounty.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*FoN8WMHvpBMsUk5wI6ckFA@2x.jpeg" /></figure><ol><li><strong>The Starting Point: A Staging Subdomain</strong></li></ol><p>I was looking at subdomains for a big company. One was staging.example.com. I always check the robots.txt file. Sometimes developers leave clues there. This one had a single, interesting entry: “Disallow: /sitebsadmin”</p><p>My first thought: “Admin panel. Let’s see if it’s locked down.”</p><p>2. <strong>The Login Page and the “IMS” Option</strong></p><p>I went to https://staging.example.com/sitebsadmin. It was a login page for Adobe Commerce. There was the usual username/password form. But there was also another button: “Login with IMS.”</p><p>IMS is their single sign-on. I clicked it. It took me to a separate login page on auth.example.com. The page looked standard. But then I saw it, right there on the login form: a link that said “Create new account.”</p><p>A huge red flag went off. Why would a staging admin panel let anyone on the internet create a new account?</p><p>3. <strong>The Exploit: Account Creation to Admin Dashboard</strong></p><p>I clicked it. I made an account with a random email. The process was normal. After confirming, it logged me in and sent me back to the site.</p><p>The page loaded. It wasn’t a user profile.</p><p>It was the full Adobe Commerce admin dashboard.</p><p>Menus for orders, customers, products, configuration — everything. I had complete access. I could see real customer information, order history, the whole system. From completely unauthenticated to full admin in about 60 seconds.</p><p>4. <strong>Why This Was So Bad (The Impact)</strong></p><p>This is called Broken Access Control or Privilege Escalation. The “Login with IMS” system was completely misconfigured. It was set up to let anyone register, and when they did, it gave them the highest privileges by default on the connected admin panel.</p><p>In the wrong hands, this access could have led to:</p><p>· Theft of all customer data (names, emails, maybe more).</p><p>· Financial fraud (issuing refunds, creating fake orders).</p><p>· Complete takeover of the staging commerce backend.</p><p>. For a company of this size, it was a critical finding.</p><p><strong>5. Reporting It (The Scary Part)</strong></p><p>I was nervous. This was my first big find. I took screenshots (blurring all the real customer data), wrote down every single step I took, and explained the impact.</p><p>I found their security report form and submitted it. I also sent a direct email to their security team to make sure they saw it.</p><p>A day later, their AppSec Project Manager replied. Just one line, but it made my week:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*qP8fX1rzRKBC7Xrg3Btk3Q@2x.jpeg" /></figure><p>They fixed it fast. A bit later, they confirmed they would patch it and reward me. My first bounty was locked in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*__B6ZVeHJorIAEItrT9Fqw@2x.jpeg" /></figure><p>6. <strong>What I Learned (So You Can Find Bugs Too)</strong></p><p>· Check robots.txt. Always. It’s not just for search engines. It’s a treasure map for hidden paths like /admin, /api, /backup, /sitebsadmin.</p><p>· Staging sites are NOT safe. Companies often forget to lock them down as hard as production. But they sometimes have real data. They are gold mines.</p><p>· Test EVERY login option. Don’t just try to hack the main form. Click the “Login with Google/Facebook/CompanySSO” button. See where it goes. Look for weird things like open registration on what should be an internal system.</p><p>· The bug might be simple. This wasn’t a fancy coding trick. It was a simple, dangerous configuration mistake. Look for the obvious stuff first.</p><p>· Don’t give up. I spent 6 months learning and finding nothing reportable. Then this happened. The process works. Keep learning, keep poking at things, and document everything clearly.</p><p><strong>7. Final Thoughts</strong></p><p>To anyone starting out: you can do this. I’m proof. Focus on learning the basics, be curious, and don’t be afraid to report what you find responsibly.</p><p>A huge thank you to the security team at the company for handling this professionally and for the bounty. It’s a great feeling to find a flaw and help get it fixed.</p><p>On to the next hunt.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=322ae07f1247" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>