<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Web on H4CK R007</title>
    <link>https://h4ckr00t.com/tags/web/</link>
    <description>Recent content in Web on H4CK R007</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 17 Apr 2026 22:47:33 +0300</lastBuildDate>
    <atom:link href="https://h4ckr00t.com/tags/web/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>HackTheBox Web Challenge: Baby Auth</title>
      <link>https://h4ckr00t.com/posts/baby-auth/</link>
      <pubDate>Fri, 17 Apr 2026 22:47:33 +0300</pubDate>
      <guid>https://h4ckr00t.com/posts/baby-auth/</guid>
      <description>Introduction In this writeup, we will explore the solution to the &amp;ldquo;Baby Auth&amp;rdquo; Web challenge from HackTheBox. This challenge is designed to test our understanding of web authentication mechanisms and how to bypass them.&#xA;Target: 154.57.164.80:32749&#xA;Solution Approach The &amp;ldquo;Baby Auth&amp;rdquo; challenge likely involves a web application with an authentication mechanism that we need to bypass. The name suggests that the authentication might be simple or &amp;ldquo;baby-like,&amp;rdquo; which could indicate weak security measures.</description>
    </item>
  </channel>
</rss>
