{"id":439,"date":"2024-10-16T22:16:24","date_gmt":"2024-10-16T20:16:24","guid":{"rendered":"https:\/\/bergee.it\/blog\/?p=439"},"modified":"2026-04-27T22:18:26","modified_gmt":"2026-04-27T20:18:26","slug":"accessing-admin-panel-with-fuzzing-digging-and-guessing","status":"publish","type":"post","link":"https:\/\/bergee.it\/blog\/accessing-admin-panel-with-fuzzing-digging-and-guessing\/","title":{"rendered":"Accessing admin panel with fuzzing, digging and guessing"},"content":{"rendered":"<p>Hello folks<\/p>\n<p>This time I want to tell you the story how I gained access to some admin functionalities\u00a0 and leaked some sensitive info using FUFF, Burp, my eyes, and brain :).<\/p>\n<h3>Fuzzing<\/h3>\n<p>Let&#8217;s call the target &#8220;redacted.com&#8221;. I started fuzzing the target with FUFF and found an <em>\/admin<\/em> endpoint<\/p>\n<blockquote><p>https:\/\/redacted.com\/app\/admin<\/p><\/blockquote>\n<p>which displayed: &#8220;Sorry you&#8217;re not authorized to access the page&#8221; when entering the site.\u00a0 I moved on to testing other parts of an application. Later, I read Sam Curry&#8217;s article on Starbucks hacking by attacking secondary contexts :<\/p>\n<p><a href=\"https:\/\/samcurry.net\/hacking-starbucks\">https:\/\/samcurry.net\/hacking-starbucks<\/a><\/p>\n<p>I recommend reading it. I entered this site again and logged all the requests. But nothing was interesting besides the endpoint which gave me 403 response in burp.\u00a0 I tried playing with this endpoint as in the the article, but I quickly realized this is not the case. However, if I appended anything after the \/admin\/ such as:<\/p>\n<blockquote><p>https:\/\/redacted.com\/app\/admin\/xxx<\/p><\/blockquote>\n<p>I&#8217;ve got 404 response, so&#8230; BINGO. It should be 403, isn&#8217;t it?.<\/p>\n<h3>More fuzzing<\/h3>\n<p>I started the FUFF again and in a minute I found the <em>\/orders<\/em> endpoint:<\/p>\n<blockquote><p>https:\/\/redacted.com\/app\/admin\/orders<\/p><\/blockquote>\n<p>which returned a code with order IDs and numbers. Ok if we have some list of orders, now there must be an endpoint to view the order details.\u00a0 I tried to look for it somewhere in JavaScript files, with no luck, though. As I was already familiar with the app, I tried to guess it. After some trial and errors I guessed both endpoint and parameter name and it was:<\/p>\n<blockquote><p>https:\/\/redacted.com\/app\/admin\/orderdetails?orderdid=1<\/p><\/blockquote>\n<p>I could view the details of the first order in the system.<\/p>\n<p>&nbsp;<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-450 size-full\" src=\"https:\/\/bergee.it\/blog\/wp-content\/uploads\/2024\/10\/order_details_redacted-2.jpg\" alt=\"\" width=\"1845\" height=\"793\" srcset=\"https:\/\/bergee.it\/blog\/wp-content\/uploads\/2024\/10\/order_details_redacted-2.jpg 1845w, https:\/\/bergee.it\/blog\/wp-content\/uploads\/2024\/10\/order_details_redacted-2-300x129.jpg 300w, https:\/\/bergee.it\/blog\/wp-content\/uploads\/2024\/10\/order_details_redacted-2-1024x440.jpg 1024w, https:\/\/bergee.it\/blog\/wp-content\/uploads\/2024\/10\/order_details_redacted-2-768x330.jpg 768w, https:\/\/bergee.it\/blog\/wp-content\/uploads\/2024\/10\/order_details_redacted-2-1536x660.jpg 1536w, https:\/\/bergee.it\/blog\/wp-content\/uploads\/2024\/10\/order_details_redacted-2-850x365.jpg 850w\" sizes=\"auto, (max-width: 1845px) 100vw, 1845px\" \/><\/p>\n<h3>Digging in js files<\/h3>\n<p>So far so good. I could report it, but if I found these two endpoints, there must be more of them. I tried to fuzz this admin endpoint some more with FUFF\u00a0 using different lists but with no luck :(. Next day with fresh mind I decided to dive into javascript files by hand. I clicked around the app , logging the requests in burp and then looking through the js files. After a while\u00a0 I found some big chunks of commented out js code. And there where some endpoints I&#8217;ve never seen before using that app. I thought that these might be some admin endpoints as they started with: delete, remove, publish, unpublish words.\u00a0 It was some kind of e-learning app, so let&#8217;s assume these endpoins were like:<\/p>\n<blockquote><p>https:\/\/redacted.com\/app\/admin\/deleteCourse<\/p>\n<p>https:\/\/redacted.com\/app\/admin\/removeCourse<\/p>\n<p>https:\/\/redacted.com\/app\/admin\/unpublishCourse<\/p>\n<p>https:\/\/redacted.com\/app\/admin\/publishCourse<\/p><\/blockquote>\n<p>Reading js files and ajax requests I could easily construct the proper requests as I had the endpoints, the methods and the parameters.<\/p>\n<h3>The POC<\/h3>\n<p>The hard part was to create the POC not damaging any data in the app. As I could not create my own course, I decided to find the endpoint which gets the course id and then based on the responses, find the one that does not exist. That was pretty easy , just using the app and logging the requests. Then I used this course id in the endpoints mentioned above. If The status code returned 200, that was the proof the endpoints were not properly secured. After some digging I found some more enpoints. I reported all the finding and was rewarded a nice bounty.<\/p>\n<p>&nbsp;<\/p>\n<p>Reward : 2000 USD<\/p>\n<p>See you next bug<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Hello folks This time I want to tell you the story how I gained access to some admin functionalities\u00a0 and leaked some sensitive info using FUFF, Burp, my eyes, and brain :). Fuzzing Let&#8217;s call the target &#8220;redacted.com&#8221;. I started fuzzing the target with FUFF and found an \/admin endpoint https:\/\/redacted.com\/app\/admin which displayed: &#8220;Sorry you&#8217;re&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1,32,29],"tags":[],"class_list":["post-439","post","type-post","status-publish","format-standard","hentry","category-bez-kategorii","category-bug-bounty","category-write-up"],"_links":{"self":[{"href":"https:\/\/bergee.it\/blog\/wp-json\/wp\/v2\/posts\/439","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bergee.it\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bergee.it\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bergee.it\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/bergee.it\/blog\/wp-json\/wp\/v2\/comments?post=439"}],"version-history":[{"count":14,"href":"https:\/\/bergee.it\/blog\/wp-json\/wp\/v2\/posts\/439\/revisions"}],"predecessor-version":[{"id":457,"href":"https:\/\/bergee.it\/blog\/wp-json\/wp\/v2\/posts\/439\/revisions\/457"}],"wp:attachment":[{"href":"https:\/\/bergee.it\/blog\/wp-json\/wp\/v2\/media?parent=439"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bergee.it\/blog\/wp-json\/wp\/v2\/categories?post=439"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bergee.it\/blog\/wp-json\/wp\/v2\/tags?post=439"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}