<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Web-Security on Akshit Kathuria</title>
    <link>https://ak-debug.github.io/tags/web-security/</link>
    <description>Recent content in Web-Security on Akshit Kathuria</description>
    <image>
      <title>Akshit Kathuria</title>
      <url>https://ak-debug.github.io/social-preview.png</url>
      <link>https://ak-debug.github.io/social-preview.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 12 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ak-debug.github.io/tags/web-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Broken Access Control: IDOR and Cookie Tampering</title>
      <link>https://ak-debug.github.io/posts/broken-access-control-idor-and-cookies/</link>
      <pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://ak-debug.github.io/posts/broken-access-control-idor-and-cookies/</guid>
      <description>When the server trusts a value the client can change to decide who you are or what you can see, you can often just change it. Here I cover two sides of broken access control: tampering with a client-side cookie to become an admin, and incrementing an ID in the URL to read someone else&amp;rsquo;s record, using two DD CTF challenges as worked examples.</description>
    </item>
    <item>
      <title>Bypassing CSRF Token Randomization Using an XSS Flaw</title>
      <link>https://ak-debug.github.io/posts/bypassing-csrf-token-randomization-with-xss/</link>
      <pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://ak-debug.github.io/posts/bypassing-csrf-token-randomization-with-xss/</guid>
      <description>Anti-CSRF tokens stop a classic cross-site request forgery attack, but they assume the attacker can&amp;rsquo;t read the page. An XSS vulnerability breaks that assumption. Here I chain a stored XSS flaw on the SEED Labs Elgg platform to exfiltrate a victim&amp;rsquo;s session cookie and CSRF tokens, then replay any authenticated action as them.</description>
    </item>
    <item>
      <title>Enumerating a Server Through an Exposed Command Interface</title>
      <link>https://ak-debug.github.io/posts/enumerating-a-server-through-command-execution/</link>
      <pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://ak-debug.github.io/posts/enumerating-a-server-through-command-execution/</guid>
      <description>When a web app hands you the ability to run shell commands, the challenge isn&amp;rsquo;t getting code execution, it&amp;rsquo;s knowing how to look around. Here I cover methodical filesystem enumeration from a command primitive, including seeing past a decoy flag to a hidden one, and why exposing command execution is total compromise.</description>
    </item>
    <item>
      <title>Exploiting XXE: Reading Local Files via XML External Entities</title>
      <link>https://ak-debug.github.io/posts/exploiting-xxe-to-read-local-files/</link>
      <pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://ak-debug.github.io/posts/exploiting-xxe-to-read-local-files/</guid>
      <description>When an application parses XML you control and its parser resolves external entities, you can make the server read local files and hand them back to you. This is XXE. Here I explain why XML parsers are dangerous by default, walk through reading a file off the server with a classic XXE payload, and cover how to shut it down.</description>
    </item>
    <item>
      <title>From File Upload to Remote Code Execution</title>
      <link>https://ak-debug.github.io/posts/file-upload-to-rce/</link>
      <pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://ak-debug.github.io/posts/file-upload-to-rce/</guid>
      <description>If a web server lets you upload a file and will later execute it, an upload form becomes a way to run your own code on the server. Here I walk through confirming PHP execution with a harmless test payload and then reading a protected file, plus why &amp;lsquo;store the upload in the webroot&amp;rsquo; is the real mistake.</description>
    </item>
    <item>
      <title>Path Traversal and LFI: Reading Files the App Never Meant to Serve</title>
      <link>https://ak-debug.github.io/posts/local-file-inclusion-and-path-traversal/</link>
      <pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://ak-debug.github.io/posts/local-file-inclusion-and-path-traversal/</guid>
      <description>When a web app takes a filename from the user and reads it off disk, a few ../ sequences can walk out of the intended directory and into anything the server can read. Here I cover path traversal end to end, including a filter-bypass trick for when the app tries to strip dangerous input, using two DD CTF challenges as worked examples.</description>
    </item>
    <item>
      <title>SQL Injection: Bypassing a Login with OR 1=1</title>
      <link>https://ak-debug.github.io/posts/sql-injection-login-bypass/</link>
      <pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://ak-debug.github.io/posts/sql-injection-login-bypass/</guid>
      <description>A login form that builds its SQL query by pasting your input into a string can be talked into authenticating you as someone else. Here I walk through turning a SQL error into a login bypass with a classic OR &amp;lsquo;1&amp;rsquo;=&amp;lsquo;1&amp;rsquo; payload, why it works at the query level, and how parameterised queries end the whole bug class.</description>
    </item>
    <item>
      <title>Stealing an Admin Session with XSS and an Out-of-Band Listener</title>
      <link>https://ak-debug.github.io/posts/stealing-admin-session-with-stored-xss/</link>
      <pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://ak-debug.github.io/posts/stealing-admin-session-with-stored-xss/</guid>
      <description>A feedback form that reflects your input and an admin who visits the links you submit is everything you need to steal the admin&amp;rsquo;s session cookie. Here I chain an XSS payload with an out-of-band listener so the victim&amp;rsquo;s browser sends their cookie to me, and explain the admin-bot pattern and the defences that break it.</description>
    </item>
    <item>
      <title>Web Recon: Finding Secrets in Source, robots.txt, and Client-Side Storage</title>
      <link>https://ak-debug.github.io/posts/web-recon-finding-client-side-secrets/</link>
      <pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://ak-debug.github.io/posts/web-recon-finding-client-side-secrets/</guid>
      <description>Developers keep hiding data in places the browser can read: HTML comments, robots.txt, hidden fields, and local storage. None of it is secret. Here I reassemble a flag split across the page source, a robots.txt disallow entry, and an inspected value, and explain why client-side is never a hiding place.</description>
    </item>
  </channel>
</rss>
