π Detailed Bug Bounty Tip: Publicly Exposed Firebase Config β Unauthorized Data Uploads
Found a juicy misconfiguration during a recon phase!
### Vulnerability:
Many web/mobile apps use Firebase Realtime Database (Google) and leave the configuration exposed in client-side JavaScript or source code. When the database security rules are not properly set (often left as default "true" for testing), anyone can read and write data without authentication.
This leads to unauthorized data injection, tampering, or even full database takeover.
### How to Test:
1. Hunt for Firebase config in JS files, source code, or APK (look for
2. Identify the database URL (usually `https://<project-id>.firebaseio.com`)
3. Test write access with a simple PUT request
### Exploitation Command:
Replace
Proof of Concept Result:
The database accepted the PUT request and stored the attacker-controlled JSON data.
### Impact:
- Data pollution / poisoning
- Injecting malicious content (e.g., XSS payloads, fake user data, phishing links)
- Potential account takeover or business logic abuse depending on how the app uses the data
- In severe cases β complete database compromise
### How to Report & Fix (for devs):
- Set proper Firebase Realtime Database Security Rules (deny read/write by default)
- Use Firebase Authentication
- Avoid exposing sensitive config in client-side code when possible
- Use Firestore with stricter rules instead (if applicable)
Pro Tip: Always check
#BugBounty #BugBountyTips #Firebase #WebAppSec #HackerOne #Bugcrowd #Pentesting #CyberSecurity
Found a juicy misconfiguration during a recon phase!
### Vulnerability:
Many web/mobile apps use Firebase Realtime Database (Google) and leave the configuration exposed in client-side JavaScript or source code. When the database security rules are not properly set (often left as default "true" for testing), anyone can read and write data without authentication.
This leads to unauthorized data injection, tampering, or even full database takeover.
### How to Test:
1. Hunt for Firebase config in JS files, source code, or APK (look for
firebaseConfig, apiKey, databaseURL, projectId etc.)2. Identify the database URL (usually `https://<project-id>.firebaseio.com`)
3. Test write access with a simple PUT request
### Exploitation Command:
curl -X PUT "https://your-project-id.firebaseio.com/poc.json" \
-d '{"POC": "Successful upload by Bug Hunter", "timestamp": "2026"}'
Replace
your-project-id with the actual one. If successful, you'll be able to inject arbitrary data into the database.Proof of Concept Result:
The database accepted the PUT request and stored the attacker-controlled JSON data.
### Impact:
- Data pollution / poisoning
- Injecting malicious content (e.g., XSS payloads, fake user data, phishing links)
- Potential account takeover or business logic abuse depending on how the app uses the data
- In severe cases β complete database compromise
### How to Report & Fix (for devs):
- Set proper Firebase Realtime Database Security Rules (deny read/write by default)
- Use Firebase Authentication
- Avoid exposing sensitive config in client-side code when possible
- Use Firestore with stricter rules instead (if applicable)
Pro Tip: Always check
.js files and network tab for firebaseio.com during recon. Many programs pay well for this!#BugBounty #BugBountyTips #Firebase #WebAppSec #HackerOne #Bugcrowd #Pentesting #CyberSecurity
β€10π7
This media is not supported in your browser
VIEW IN TELEGRAM
π24πΏ3β€1
π‘οΈ Bug Bounty Tip: Test IDOR + Web Cache Deception Together
When hunting IDORs, always check for web cache deception on the same endpoints:
1. As User A, access a sensitive resource like
2. As User B, repeat the exact same URL with identical headers.
3. Only change the Cookie/Auth token.
If User B receives User A's 200 OK response from cache β you've likely found a critical vulnerability!
This combo can lead to account takeover-level impacts.
#BugBounty #AppSec #WebSecurity #IDOR #Pentesting
When hunting IDORs, always check for web cache deception on the same endpoints:
1. As User A, access a sensitive resource like
/api/invoices/123 (also try appending .css or `.js`).2. As User B, repeat the exact same URL with identical headers.
3. Only change the Cookie/Auth token.
If User B receives User A's 200 OK response from cache β you've likely found a critical vulnerability!
This combo can lead to account takeover-level impacts.
#BugBounty #AppSec #WebSecurity #IDOR #Pentesting
β€13π4π₯1
Forwarded from Brut Security 2.0
This media is not supported in your browser
VIEW IN TELEGRAM
π΄ Another serious security vulnerability has been discovered in Redis 8.8.0, and no POC has been released yet for this bidirectional RCE found by v12sec.
β€7π₯3
This media is not supported in your browser
VIEW IN TELEGRAM
π₯TORLINK: A torrent finder that runs right from your terminal with zero setup and nothing to configure.
One search checks a small curated list of sources at once. Pick what you want, and it downloads directly to your computer.
GitHub: https://github.com/baairon/torlink
One search checks a small curated list of sources at once. Pick what you want, and it downloads directly to your computer.
GitHub: https://github.com/baairon/torlink
β€6π1
This media is not supported in your browser
VIEW IN TELEGRAM
π₯ Chrome RCE PoC: CVE-2026-6307
A working renderer RCE Proof of Concept for CVE-2026-6307 β a V8 type-confusion bug (JS-to-Wasm deoptimization) patched in Chrome 147.0.7727.101.
β Full primitives (addrof/fakeobj, out-of-cage, in-cage r/w)
β No-ASLR RCE that patches JIT code to pop xcalc
β Based on Nebula Security writeup
β Heavily improved with frontier LLMs + human direction (4-day experiment)
This is renderer-only and still far from fully weaponized, but great for learning and research.
π₯ PoC + scripts:
https://github.com/0xsha/CVE-2026-6307
#Chrome #V8 #Exploit #CVE #SecurityResearch
A working renderer RCE Proof of Concept for CVE-2026-6307 β a V8 type-confusion bug (JS-to-Wasm deoptimization) patched in Chrome 147.0.7727.101.
β Full primitives (addrof/fakeobj, out-of-cage, in-cage r/w)
β No-ASLR RCE that patches JIT code to pop xcalc
β Based on Nebula Security writeup
β Heavily improved with frontier LLMs + human direction (4-day experiment)
This is renderer-only and still far from fully weaponized, but great for learning and research.
π₯ PoC + scripts:
https://github.com/0xsha/CVE-2026-6307
#Chrome #V8 #Exploit #CVE #SecurityResearch
β€4π₯2
βΊοΈYour support keeps me motivated to share more valuable content! If you found this helpful, drop a like & send stars β to help me keep going.
π¬ For queries, message me on Telegram: @wtf_brut
π For course enrollment, reach out on WhatsApp: wa.link/brutsecurity
π¬ For queries, message me on Telegram: @wtf_brut
π For course enrollment, reach out on WhatsApp: wa.link/brutsecurity
Telegram
Saumadip Mandal
Founder & Mentor of Brut Security
1β€5π3
Forwarded from Brut Security (Saumadip Mandal)
157 Methods for Privilege Escalation (WindowsLinuxMacos) PDF.pdf
84.9 MB
π10β€3π€2
Something is coming soon. Stay Tuned!β οΈ
Please open Telegram to view this post
VIEW IN TELEGRAM
β€4
Please do share and like . Thanks πβ€οΈ
Please open Telegram to view this post
VIEW IN TELEGRAM
β€3π1π₯1
I am sharing 10 additional coupons on LinkedIn upon reaching 12,000 followers (60 remaining). π«π
https://www.linkedin.com/posts/mandal-saumadip_cybersecurity-bugbounty-ethicalhacking-share-7479612184960909313-sG9F/
Please follow and like; the coupon will be available in the comments after reaching 12k followers. β±οΈπ¬
Thank you to everyone who participated today! π
https://www.linkedin.com/posts/mandal-saumadip_cybersecurity-bugbounty-ethicalhacking-share-7479612184960909313-sG9F/
Please follow and like; the coupon will be available in the comments after reaching 12k followers. β±οΈπ¬
Thank you to everyone who participated today! π
LinkedIn
2026 Bug Bounty Guide - Brut Security | Saumadip Mandal posted on the topic | LinkedIn
π₯ Just dropped β 2026 Bug Bounty Guide
π 86 pages. 25 chapters. Built on real data.
π’What's inside:
β The AI shift β what it means for your bounties
β Full recon workflow (subfinder β puredns β httpx β nuclei)
β Every major vuln class with payloads β XSSβ¦
π 86 pages. 25 chapters. Built on real data.
π’What's inside:
β The AI shift β what it means for your bounties
β Full recon workflow (subfinder β puredns β httpx β nuclei)
β Every major vuln class with payloads β XSSβ¦
β€2π₯2π1
The open-source AI pentesting tool. Autonomous AI hackers that find and fix your appβs vulnerabilities.
Resource: github.com/usestrix/strix
Resource: github.com/usestrix/strix
β€4π4
Please open Telegram to view this post
VIEW IN TELEGRAM
π₯6β€3π1
π Admissions Open | Upcoming Cybersecurity Batches
Enrollment is now open for our upcoming batches:
β’ Web Penetration Testing
β’ Bug Bounty Hunting
β’ Ethical Hacking
β’ VAPT (Vulnerability Assessment & Penetration Testing)
What you'll get:
β Live practical sessions
β Real-world labs
β Industry methodology
β Mentor support
β Certificate on completion
π Student Discount Available (Limited Time)
π© DM to enroll or visit: http://wa.link/brutsecurity
Enrollment is now open for our upcoming batches:
β’ Web Penetration Testing
β’ Bug Bounty Hunting
β’ Ethical Hacking
β’ VAPT (Vulnerability Assessment & Penetration Testing)
What you'll get:
β Live practical sessions
β Real-world labs
β Industry methodology
β Mentor support
β Certificate on completion
π Student Discount Available (Limited Time)
π© DM to enroll or visit: http://wa.link/brutsecurity
β€2π₯1
π₯ KeyHunter: A fast Rust tool for finding leaked API keys across public GitHub repos.
It supports 45+ providers and can verify which exposed secrets are still active.
GitHub: https://github.com/fadidevv/keyhunter
It supports 45+ providers and can verify which exposed secrets are still active.
GitHub: https://github.com/fadidevv/keyhunter
π2β€1