{"id":15,"date":"2026-01-15T17:20:52","date_gmt":"2026-01-15T17:20:52","guid":{"rendered":"https:\/\/zerotoghost.com\/?p=15"},"modified":"2026-01-15T23:14:55","modified_gmt":"2026-01-15T23:14:55","slug":"hackthebox-academy-web-fuzzing","status":"publish","type":"post","link":"https:\/\/zerotoghost.com\/?p=15","title":{"rendered":"HackTheBox Academy – Web Fuzzing"},"content":{"rendered":"\n

(Sections 1 and 2 coming soon)<\/em><\/p>\n\n\n\n

NOTE<\/strong>: I have blurred out any secret values and flags. There are plenty of walkthroughs that chose to leave them in there, but I think half the fun is figuring it out. Hopefully this helps you get unstuck while you’re working through the module yourself.<\/em><\/p>\n\n\n\n

3.1 Parameter and Value Fuzzing<\/h2>\n\n\n\n

GET Parameters : Openly Sharing Information<\/p>\n\n\n\n

https://example.com\/search?query=fuzzing&category=security<\/code><\/pre>\n\n\n\n
When you see GET parameters in the URL (following a question(?) mark, this is often a signal that you can modify the request to retrieve different information. In web application testing, I would check for tenant and user enumeration, along with information I shouldn’t be able to access with my provided permissions.<\/p>\n\n\n\n
\"\"
Get request for provided IP address<\/figcaption><\/figure>\n\n\n\n
The tutorial instructs us to use wenum<\/strong>, but as I don’t already have that installed on my machine I’m using wfuzz<\/strong>. It’s a similar tool. Using the equivalent command and recommended wordlist, we get a successful response. <\/p>\n\n\n\n
Remember – your IP, port, and wordlist location is likely different than mine.<\/em><\/p>\n\n\n\n
wfuzz -w \/usr\/share\/wordlists\/dirb\/common.txt --sc 200 -u http:\/\/94.237.123.85:37328\/get.php?x=FUZZ<\/code><\/pre>\n\n\n\n
Using cURL<\/strong>, we can retrieve the flag for question 1.<\/p>\n\n\n\n
\"\"
Successful fuzzing response<\/figcaption><\/figure>\n\n\n\n
curl http:\/\/94.237.123.185:37328\/get.php?x=XXXX<\/code><\/pre>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Next, we are given some information on POST requests. Unlike a GET request, which (like the name) retrieves information, a POST request sends data. This can be a login portal (username and password), a form, or even a blog post. The parameters are in the body of the request, unlike our example get request which had parameters in the URL portion.<\/p>\n\n\n\n
\"\"
Here the response is telling us we didn’t include the expected parameters<\/figcaption><\/figure>\n\n\n\n
Next we use FFUF (one of my favorite tools) to fuzz the post parameter y. Note the content-type flag – it will not work without it. I tried finding a list of acceptable content-types on FFUF’s github page, but for now we just take HTB’s word for it.<\/p>\n\n\n\n
ffuf -u http:\/\/94.237.123.185:37328\/post.php -X POST -H \"Content-Type: application\/x-www-form-urlencoded\" -d \"y=FUZZ\" w \/usr\/share\/wordlists\/dirb\/common.txt<\/code><\/pre>\n\n\n\n
This results in one successful result<\/p>\n\n\n\n
\"\"
Using FFUF to fuzz post parameters<\/figcaption><\/figure>\n\n\n\n
And voila! We have our second flag.<\/p>\n\n\n\n
curl -d \"y=Sxxxxxx\" http:\/\/94.237.185:37328\/post.php<\/code><\/pre>\n\n\n\n
\"\"<\/figure>\n\n\n\n
4.1 Virtual Host and Subdomain Fuzzing<\/h2>\n\n\n\n
Subdomains vs virtual hosts (vhost)<\/p>\n\n\n\n
    \n
  • Identification<\/span>: Vhosts<\/strong> are identified in the HOST header in a HTTP request, where subdomains<\/strong> are identified by DNS records.<\/li>\n\n\n\n
  • Purpose<\/span>: Vhosts<\/strong> are used to host multiple websites on a single server, subdomains<\/strong> are used to organize sections\/services within a website.<\/li>\n\n\n\n
  • Security risks<\/span>: misconfigured vhosts<\/strong> can expose internal applications or sensitive data, subdomain<\/strong> takeover vulnerabilities can occur if DNS records are mismanaged <\/li>\n<\/ul>\n\n\n\n
    Gobuster vhost fuzzing command<\/p>\n\n\n\n
    gobuster vhost -u http:\/\/inlanefreight.htb -w \/usr\/share\/wordlists\/dirb\/common.txt --append-domain\n<\/code><\/pre>\n\n\n\n
    For question 1, we are asked to simply fuzz vhosts for the provided target. NOTE: You will need to edit your hosts file and use the url http:\/\/inlanefreight.htb in the above command.<\/p>\n\n\n\n
    \"\"
    Fuzzing for vhosts with gobuster<\/figcaption><\/figure>\n\n\n\n
    For question 2, we need to repeat the process but instead of vhosts we are fuzzing for subdomains. The syntax is:<\/p>\n\n\n\n
    gobuster dns --domain inlanefreight.com -w \/usr\/share\/wordlists\/amass\/subdomains-top1million-5000.txt<\/code><\/pre>\n\n\n\n
    Note: the module uses -d, but gobuster now uses -d for delay so the correct syntax is –do or –domain<\/em>. ALSO – this one is .com<\/strong> not .htb<\/em><\/p>\n\n\n\n
    \"\"
    Successful Gobuster subdomain enumeration for inlanefreight.com<\/figcaption><\/figure>\n\n\n\n
    5.1 Filtering Fuzzing Output<\/h2>\n\n\n\n
    If you’ve used FFUF, Gobuster or wfuzz before you know sometimes you get an insane amount of results. I always will run the command without filters, and then typically filter by size for the default response (such as a redirect to login page with a size of 874).<\/p>\n\n\n\n
    Gobuster<\/strong><\/p>\n\n\n\n
      \n
    • -s (include) – only include responses with specific status codes (200, 301, etc)<\/s> no longer valid flag<\/li>\n\n\n\n
    • -b (exclude) – exclude responses with specific status codes (404, 403)<\/s> no longer valid flag<\/li>\n\n\n\n
    • –exclude-length – exclude responses with specific length (0, 874, 1290…)<\/li>\n\n\n\n
    • –exclude-status – exclude response with specific status (403)<\/li>\n<\/ul>\n\n\n\n
      Example:<\/p>\n\n\n\n
      gobuster dir -u http:\/\/example.com\/ -w wordlist.txt -s 200,301 --exclude-length 0<\/code><\/pre>\n\n\n\n
      FFUF<\/strong><\/p>\n\n\n\n
        \n
      • -mc (match code) – include only specific codes (200, 301)<\/li>\n\n\n\n
      • -fc (filter code) – exclude specific codes<\/li>\n\n\n\n
      • -fs (filter size) – exclude specific page size<\/li>\n\n\n\n
      • -ms (match size) – include only specific page size<\/li>\n\n\n\n
      • -fw (filter word count) – filter out number of words in response<\/li>\n\n\n\n
      • -mw (match word count)<\/li>\n\n\n\n
      • -fl (filter line) – exclude response with specific number of lines, or range of lines.<\/li>\n\n\n\n
      • -ml (match line)<\/li>\n\n\n\n
      • -mt (match time) – include only responses that meet a specific time-to-first-byte (TTFB) condition. Used to filter responses with unusually slow or quick responses. ( >500)<\/li>\n<\/ul>\n\n\n\n
        Optional exercise:<\/p>\n\n\n\n
        Fuzz the post parameter for the target. I simply reused the FFUF command from 3.1 part 2. After cURLing the target, I noticed the post parameter was again “y”.<\/p>\n\n\n\n
        ffuf -u http:\/\/94.237.63.174:36026\/post.php -X POST -H \"Content-Type: application\/x-www-form-urlencoded\" -d \"y=FUZZ\" -w \/usr\/share\/wordlists\/dirb\/common.txt<\/code><\/pre>\n\n\n\n
        \"\"
        Fuzzing success<\/figcaption><\/figure>\n\n\n\n
        \"\"
        Successful flag!<\/figcaption><\/figure>\n\n\n\n
        6.1 Validating Findings<\/h2>\n\n\n\n
        Fuzzing can provide potential leads, but not every result is a genuine vulnerability. It’s important to check for false positives (IE, in my job I check discovered domains in browser or with cURL). It’s important to validate any finding tooling reports, in general.<\/p>\n\n\n\n
        Example: you discover a directory \/backup\/ while fuzzing a webserver. While this may have returned a 200 response code, you should still enumerate the directory to see if any information actually exists or if it is use.<\/p>\n\n\n\n
        Question 1: Fuzz the target system using directory-list-2.3-medium.txt, looking for a hidden directory. Once found, responsibly determine the validity of the vulnerability by analyzing the tar.gz file.<\/p>\n\n\n\n
        \"\"
        Fuzzing target<\/figcaption><\/figure>\n\n\n\n
        And then validate with cURL:<\/p>\n\n\n\n
        \"\"
        Using cURL to check content-length of discovered file<\/figcaption><\/figure>\n\n\n\n
        7.1 Web APIs<\/h2>\n\n\n\n
        A web API (application programming interface) is a set of rules and specifications that enable different software applications to communicate over the web. Essentially, an API is a bridge between a server and client (browser, mobile app) that wants to access or utilize the data. <\/p>\n\n\n\n
        REST APIs<\/strong><\/p>\n\n\n\n
        Representational State Transfer (REST) APIs are popular architecture for building web services. They use a stateless<\/strong>, client-server communication module. These utilize standard HTTP methods (GET, POST, PUT, DELETE) to perform CRUD (Create, Read, Update, Delete) operations on resources. This is typically done in lightweight formats such as JSON or XML.<\/p>\n\n\n\n
        Example query: <\/p>\n\n\n\n
        GET \/users\/123\n<\/code><\/pre>\n\n\n\n
        SOAP APIs<\/strong><\/p>\n\n\n\n
        Simple Object Access Protocol (SOAP) APIs follow a more standardized protocol. They use XML to define messages, which are encapsulated in “SOAP envelopes” and transmitted using protocols like HTTP or SMTP. SOAP APIs often include built-in security, reliability and transaction management features.<\/p>\n\n\n\n
        Example query:<\/p>\n\n\n\n
        <soapenv:Envelope xmlns:soapenv=\"http:\/\/schemas.xmlsoap.org\/soap\/envelope\/\" xmlns:tem=\"http:\/\/tempuri.org\/\">\n   <soapenv:Header\/>\n   <soapenv:Body>\n      <tem:GetStockPrice>\n         <tem:StockName>AAPL<\/tem:StockName>\n      <\/tem:GetStockPrice>\n   <\/soapenv:Body>\n<\/soapenv:Envelope>\n<\/code><\/pre>\n\n\n\n
        GraphQL<\/strong><\/p>\n\n\n\n
        GraphQL provides a single endpoint where clients can request data. Introspection makes it easier to evolve APIs over time without breaking exisiting clients.<\/p>\n\n\n\n
        Example query:<\/p>\n\n\n\n
        query {\n  user(id: 123) {\n    name\n    email\n  }\n}<\/code><\/pre>\n\n\n\n
        7.2 Identifying Endpoints<\/h2>\n\n\n\n
        REST APIs <\/strong>are built around the concept of resources, identified by unique URLs called endpoints.<\/p>\n\n\n\n
        Structured as URLs representing the resource you want to access. Ex:<\/p>\n\n\n\n
          \n
        • \/users – collection of user resources<\/li>\n\n\n\n
        • \/users\/123 – represents a specific user with ID 123<\/li>\n\n\n\n
        • \/products – collection of product resources<\/li>\n\n\n\n
        • \/users?limit=10&sort=name – (query ressouce) show 10 users, sorted by name<\/li>\n\n\n\n
        • \/products\/{id}pen_spark – (path parameters) identifies a specific resource<\/li>\n\n\n\n
        • { “name” : “New Product”, “price” : 99.00 } – sent in body of POST, PUT, PATCH requests<\/li>\n<\/ul>\n\n\n\n
          Discovering REST Endpoints and Parameters<\/strong><\/p>\n\n\n\n
            \n
          • API documentation<\/li>\n\n\n\n
          • Network Traffic Analysis (burp suite)<\/li>\n\n\n\n
          • Parameter Name Fuzzing (FFUF, wfuzz)<\/li>\n<\/ul>\n\n\n\n
            SOAP APIs rely on XML-based messages and Web Services Description Language (WSDL) files to define their interfaces and operations.<\/p>\n\n\n\n
            A WSDL file might define an operation called SearchBooks with the following parameters:<\/p>\n\n\n\n
              \n
            • keywords (string): The search term to use<\/li>\n\n\n\n
            • author (string): The name of the author (optional)<\/li>\n\n\n\n
            • genre (string): The genre of the book (optional)<\/li>\n<\/ul>\n\n\n\n
              <soapenv:Envelope xmlns:soapenv=\"http:\/\/schemas.xmlsoap.org\/soap\/envelope\/\" xmlns:lib=\"http:\/\/example.com\/library\">\n   <soapenv:Header\/>\n   <soapenv:Body>\n      <lib:SearchBooks>\n         <lib:keywords>cybersecurity<\/lib:keywords>\n         <lib:author>Dan Kaminsky<\/lib:author>\n      <\/lib:SearchBooks>\n   <\/soapenv:Body>\n<\/soapenv:Envelope>\n<\/code><\/pre>\n\n\n\n
              Discovering SOAP endpoints and paameters<\/p>\n\n\n\n
                \n
              • WSDL analysis – describes available operations (endpoints), Input parameters, output parameters, data types, location (URL) of endpoint<\/li>\n\n\n\n
              • Network traffic anaylsis<\/li>\n\n\n\n
              • Fuzzing parameter names and values<\/li>\n\n\n\n
              • <\/li>\n<\/ul>\n\n\n\n
                7.3 API Fuzzing<\/h2>\n\n\n\n
                I love API testing. It’s an integral part of many web applications, and while it *CAN* be repetitive, there’s something beautiful about the process.<\/p>\n\n\n\n
                API fuzzing is a specialized form of fuzzing tailored for web APIs. While the core principles of fuzzing are the same – API fuzzing focuses on unique structure and protocols used by APIs. <\/p>\n\n\n\n
                  \n
                • Altering parameter values<\/li>\n\n\n\n
                • Modifying request headers<\/li>\n\n\n\n
                • Changing the order of parameters<\/li>\n\n\n\n
                • Introducing unexpected data types or formats<\/li>\n<\/ul>\n\n\n\n
                  Why fuzz APIs?<\/p>\n\n\n\n
                    \n
                  • Uncover hidden vulnerabilities<\/li>\n\n\n\n
                  • Test robustness<\/li>\n\n\n\n
                  • Automate security testing<\/li>\n\n\n\n
                  • Simulate real-world attacks<\/li>\n\n\n\n
                  • Parameter fuzzing<\/li>\n\n\n\n
                  • Data format fuzzing<\/li>\n\n\n\n
                  • Sequence fuzzing<\/li>\n<\/ul>\n\n\n\n
                    PandaSt0rm<\/p>\n\n\n\n
                    git clone https:\/\/github.com\/PandaSt0rm\/webfuzz_api.git\ncd webfuzz_api\npip3 install -r requirements\npython3 api_fuzzer.py http:\/\/IP:PORT<\/code><\/pre>\n\n\n\n
                    \"\"<\/figure>\n\n\n\n
                    \"\"<\/figure>\n\n\n\n
                    And we got it!<\/p>\n\n\n\n
                    \"\"<\/figure>\n\n\n\n
                    8.1 Skills Assessment<\/h2>\n\n\n\n
                    We aren’t given much information – just follow the steps already laid out in the module and that ‘common.txt’ will have everything we need. Starting with FFUF (I did have to re-run this and add the -e extensions flag):<\/p>\n\n\n\n
                    ffuf -u http:\/\/IP:PORT\/FUZZ -w \/usr\/share\/wordlists\/dirb\/common.txt -recursion -recursion-depth 3 -e .html,.php<\/code><\/pre>\n\n\n\n
                    \"\"
                    FFUF output 1\/2<\/figcaption><\/figure>\n\n\n\n
                    \"\"
                    FFUF output 2\/2<\/figcaption><\/figure>\n\n\n\n
                    We find a directory and 3 endpoints – cURLing them results in this clue, telling us an invalid parameter<\/p>\n\n\n\n
                    \"\"<\/figure>\n\n\n\n
                    Run FFUF again, fuzzing the directory\/page.php?{parameter}=FUZZ gives us a valid parameter to use.<\/p>\n\n\n\n
                    \"\"<\/figure>\n\n\n\n
                    And using cURL we have a hint on where to go next. cURLing the newly discovered endpoint gives us a new hint (not pictured, you get the idea).<\/p>\n\n\n\n
                    \"\"<\/figure>\n\n\n\n
                    We use gobuster to fuzz for vhosts and discover a new endpoint (and add to \/etc\/hosts).<\/p>\n\n\n\n
                    \"\"<\/figure>\n\n\n\n
                    Inspect this in the web browser for a hint, and then another hint \ud83d\ude42<\/p>\n\n\n\n
                    After using recrusion with our discovered vhost – use at least 3 levels – you will find the page you’re looking for. Inspecting it gives you the flag, and final piece needed to finish the module.<\/p>\n\n\n\n
                    ffuf -u http:\/\/vhost.discoveredHost.hth\/PORT\/directory\/FUZZ -w common.txt -recursion -recursion-depth 5 -fc 403,404<\/code><\/pre>\n\n\n\n
                    \n
                    \"\"<\/figure>\n<\/figure>\n\n\n\n
                    \"\"<\/figure>\n\n\n\n
                    And there you have it! If you finished this module, leave a comment with any tips or hang-ups you experienced.<\/p>\n","protected":false},"excerpt":{"rendered":"
                    (Sections 1 and 2 coming soon) NOTE: I have blurred out any secret values and flags. There are plenty of walkthroughs that chose to leave them in there, but I think half the fun is figuring it out. Hopefully this helps you get unstuck while you’re working through the module…<\/p>\n","protected":false},"author":1,"featured_media":49,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[6,7,5],"class_list":["post-15","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-htb-academy","tag-ffuf","tag-fuzzing","tag-wfuzz"],"_links":{"self":[{"href":"https:\/\/zerotoghost.com\/index.php?rest_route=\/wp\/v2\/posts\/15","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zerotoghost.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zerotoghost.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zerotoghost.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/zerotoghost.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=15"}],"version-history":[{"count":9,"href":"https:\/\/zerotoghost.com\/index.php?rest_route=\/wp\/v2\/posts\/15\/revisions"}],"predecessor-version":[{"id":73,"href":"https:\/\/zerotoghost.com\/index.php?rest_route=\/wp\/v2\/posts\/15\/revisions\/73"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/zerotoghost.com\/index.php?rest_route=\/wp\/v2\/media\/49"}],"wp:attachment":[{"href":"https:\/\/zerotoghost.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=15"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zerotoghost.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=15"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zerotoghost.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=15"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}