WordPress Vulnerabilities

[@data_eng_tuts]

Please continue this wordpress series - Thank you 😊

[@c1ph3rpunk]

Back when I did testing, I had a standing rule: if I was able to get into your WP instance, it became mine to do with as I please.

[@rajeebrath5003]

How please explain,?

[@thygod4920]

Managed to find two XSS solely from a website having outdated wordpress plugins, managed to enumerate their users as well. Quite fun.

[@jxkz7]

Where can i learn.

[@sierragutenberg]

8:56 what did you write behind your webcam?

[@MayorTV1]

Wow u have the skills 🔥🔥🔥

[@Boolap1337]

Ty for the content. A suggestion - Maybe get a green screen or reduce the size of your camera? It often covers a lot of interesting details.

[@Improvise272]

That was good but in a real world scenario nobody will have a default credentials like alex:alex

[@hpesojzenitram]

You'd be surprised how common it is to get users with weak or default passwords in the real world.

[@AppSecExplained]

Actually you'd be surprised they often do, and we can brute force for days if needed. This also doesn't account for credential stuffing and password resuse either.

[@stefanjohansson2373]

Often it’s impossible to select weak passwords, but sadly a lot of weak credentials is still in use and also very common.

[@sungodd63]

Incorrect

[@mghell34]

Aw you would be surprised ahahahaha

[@johnpieter9608]

I tried this, and got an error for too many requests too quickly. How can I increase the time between each attempt? Thanks

[@mattchiles771]

Excellent - Looking forward to Part 2

[@Wolfyhack]

On the other hand, enumerating the login and brute-force password becomes more complex if the wp-admin page is protected by 2FA. What's more, if the website is behind a nginx reverse proxy with an htpasswd file on wp-admin and the entire infrastructure is behind cloudflare with active waf, the security of the wp-admin page increases by one level.😅

[@data_eng_tuts]

Yes, you are right 😅

[@X1Aman1X]

PART 2 NEEDED

[@dimuthdeja7859]

can you write the compleate command of FUFF you used. Wordlist file name is not visible.

[@fjgorringarcia]

same issue here, not visible because your face-video is on top

[@CousinFeetus]

it can be any file name. you name it when you create it and add the list of passwords. you need to get a list of passwords first and name the file to what ever you want.

[@freeloaderuser6793]

Me who has a wordpress website: *nervous sweats*

[@powerball200]

Please tell does WordPress have future? I'm learning it

[@freeloaderuser6793]

@powerball200 for now at least it still does. They'd have to make a ton of bad decisions for it to get replaced rn

[@diego-is-me7323]

when i wpscan a website it gives me an username but when i try that wp weakness that you said it say that the username doesn't exist

[@jsjs-v4e]

thx for the video, when you gonna post part 2

[@Z0nd4]

Excellent content. Greetings for Argentina!

[@میمشین-ث1ث]

if there be no limitations for pass trying burp suite is also a good option

[@TACDetective]

I hope theres a part three explaining how to avoid being hacked 🙂

[@-it759]

probably just have a strong password. there is no way to brute force if you have strong pw.

[@b1rdy0xf]

@@-it759 I would say staying up to date and using as small number of plugins as possible is more important.... or just don't use wp.

[@freeloaderuser6793]

@@b1rdy0xf The alternative is learning how to make a website from scratch. I'd argue that's more of a hassle and you're more likely to screw something up that way than through wordpress.

[@thygod4920]

@@freeloaderuser6793 CMS Like wordpress are more secure and easier to setup than making from scratch, especially when you can't afford to have a single vulnerability/exploit out in the open. For wordpress at least they have researchers willing to disclose vulns/exploits without abusing them. You wont have the same liberty in a home made one.

[@arsenijen9797]

Do you maybe wish An Music wish

[@HabibouChaibouAssoumana]

How did you get the rockyou file ?

[@spike666spike666]

How do you paste the code into the YML? whats the command keys?

[@chunibyuurikkagamesreplays3238]

What is the terminal used called ?

[@rookiesmarts]

Nice.. Thanks 👍

[@esam71]

Is it possible without wordlist?

[@CousinFeetus]

No.

[@polym3r255]

you guys really need to increase mic volume

[@AliAligas]

When I try that I had this error: no matching manifest for Linux/386 in the manifest list entries 😢😢 I don't know how to fix that any help plzz😊😊

[@justchecking12]

I am looking forward to see part2

[@akashlele8987]

Waiting for part 2

[@elaygabay9470]

i try to do what you did with the password and user brut force and i got that message: Error: Unknown response received Code: 409 what does it mean?

[@suwro]

why sudo to anything, you don't need sudo to edit docker-compose or to run your container....

[@AzlaanTKD]

How do I save it

[@irishbloke99]

Great video but When is part2?

[@terrorjackson]

Can you wpscan https?

[@Dahlah.FightMe]

Nice Sir :D

[@AUBCodeII]

First of all, I am Vegeta.

[@enigma.better]

yo i just noticed, you kinda look like ed snowden

[@sanskarkalra7966]

Love 💖😘

[@MehediHasan-pv4em]

You just kidding with us😂

[@austynstephens9263]

Alex, I must say, you look better with a beard, no homo.

[@ickschreiber3493]

bro my pc took 1 minute to brute force 200 passwords

[@sanskarkalra7966]

Z aust TFT capacitive touchscreen and then you are

[@sanskarkalra7966]

REUN

[@sanskarkalra7966]

So

[@Pardubky]

kids

[@neworig]

parsing C:\Users\Administrator\docker-compose.yml: yaml: line 16: mapping values are not allowed in this context when try to do docker-compose up this error will show up this is the yaml file version: "3" services: database: image: mysql restart: always environment: MYSQL_ROOT_PASSWORD: wppassword MYSQL_DATABASE: wpdb MYSQL_USER: wpuser MYSQL_PASSWORD: wppassword volumes: - mysql:/var/lib/mysql wordpress: depends_on: - database image: wordpress: latest restart: always ports: - "80:80" enviorment: WORDPRESS_DB_HOST: database:3306 WORDPRESS_DB_USER: wpuser WORDPRESS_DB_PASSWORD: wppassword WORDPRESS_DB_NAME: wpdb volumes: ["./:/var/www/html"] volumes: mysql: {}