
This video is a comprehensive, real-world penetration testing walkthrough, showing the process from scratch all the way to gaining admin access on a target system. The creator condenses a one-hour session into a 30-minute video to keep things engaging and efficient, but leaves the footage unedited so beginners can follow every step and learn how to apply the techniques themselves.
"In the name of God, this video is a penetration testing experiment."
"If you feel the video is fast, you can pause and go back, look at the screen, and understand like everyone else."
"Even the environment is freshly installed, nothing is ready, so we start from zero."
"If you feel the video is hard, that's normal. Step by step, it will become as easy as water."
"If you follow the previous videos, you'll be ready when you get here."
"The course isn't over, but why do a penetration test in the middle? So learners can evaluate their performance, and those who haven't hacked before can get a general idea."
"I decided to do this video as if I'm a beginner, in a new environment, not knowing anything, learning with you."
"As we learned before, when you do a penetration test, you need to be organized so you know how to examine the target."
"Most people just show you the final result. I want to show you how much work goes in before that."
"I'm entering inputs incorrectly to see if the backend filters them, or if I can talk to the server any way I want."
"Websites are made of frontend and backend. The frontend is what you see, the backend is mostly programming and databases."
"I prefer browser extensions because they're the fastest way to get information."
"We saw Apache with a specific version, found some emails, saw the HTTP server and its version, and the IP address."
"I was saving info in the terminal, which is bad. I decided to open a note and put the data there. Usually, I store data in bigger, more organized places."
"We tried to find out what technologies the site uses."
"SearchSploit is like a database of all vulnerabilities. You search for a specific technology and see if it's in the database."
"If the vulnerability exists, hacking becomes very easy. You just search for the exploit online and use it."
"We saw OpenSSH on port 22 with a certain version. I searched for vulnerabilities for that version."
"I tried to find the admin page, but I was just typing random words. I wanted to see the error page, because if it's not well-handled, it can show you information."
"I found a tool called Dirb. It needs a wordlist, so I searched for one and found 'general'."
"If the error page isn't handled well, it can show you information. Since they didn't handle errors well, it's likely they didn't hide other pages either."
"If you get errors, stop and ask yourself what's wrong. There's nothing wrong with searching for help."
"I checked robots.txt to see if there are pages the site doesn't want search engines to visit. These are usually sensitive pages."
"CMS is the framework behind the site. You need to know which CMS is used to help you build the site faster."
"The tool I used for finding pages wasn't good, so I looked for another one and found 'ffuf'."
"If you don't know a tool, go to its official page or manual and see how to use it."
"I found a subdomain called 'crm' and a brand called 'Dolibarr'. I searched for what Dolibarr is."
"I tried the default login information, and boom! It worked. They didn't change the default credentials."
"This is a weakness. The admin should have changed these credentials."
"I searched Google and found it's 'admin:admin'."
"I searched for Dolibarr vulnerabilities in Metasploit and SearchSploit."
"I found a CVE with a score of 8.8. That's a very high vulnerability. If you exploit it, you can control the whole server."
"There are people who hacked it before me. I can learn from them and see what vulnerabilities worked for them."
"I found an exploit on GitHub. The README file explains how to use it."
"If the script doesn't work, you might have to fix it yourself. Most hackers give up at this point because it's tiring to fix someone else's code."
"Since the script didn't work, I decided to exploit it manually. You have to really understand the vulnerability to do it by hand."
"I tried to create a new page in the CMS. You have to configure it, enter specific information, and sometimes trick it into letting you create a page you control."
"Just finding the default credentials is a vulnerability by itself. You can stop there, that's already a big win."
"The rest is just for those who want to go deeper. Creating a page and configuring it is more advanced and not necessary for beginners."
"If you found this hard, that's normal. With time, it will become easy."
"The best way to learn is to see examples, then explanations, then more examples."
"You'll always face new things. If you don't know something, search for it and learn."
"If you found this easy, that means you're on the right track!"
| Step | Tools/Concepts | Key Points |
|---|---|---|
| Info Gathering | Browser extensions, notes | Collect all possible data, organize findings |
| Tech & Vuln Scanning | SearchSploit, Google | Look for known vulnerabilities in used tech |
| Directory Enumeration | Dirb, ffuf, robots.txt | Find hidden pages, admin panels, sensitive files |
| CMS Identification | Manual checks, Google | Knowing the CMS helps in finding specific exploits |
| Subdomain Discovery | ffuf, manual search | Subdomains can have their own vulnerabilities |
| Exploitation | Metasploit, GitHub scripts | Try public exploits, fix scripts if needed, or exploit manually |
| Gaining Admin | Default creds, CMS config | Default credentials are a huge weakness; deeper exploitation is more advanced |
"With time and practice, you'll get better. Don't give up if you get stuck—search, learn, and keep going!" 🚀
Keywords:
Remember:
If you want to go deeper, check out the creator's other videos for more advanced techniques
Get instant summaries with Harvest