ar
Feedback

لا تقع ضحية للمخادعين! تيليمتريو يكتشف ويُميّز هذه القنوات 👉 إذا كنت تريد رؤية العلامة، اشترك

Bug Bounty - GitBook

Bug Bounty - GitBook

الذهاب إلى القناة على Telegram

Everything 4 bug bounty

إظهار المزيد
Buy Ad
8 149
المشتركون
-124 ساعات
+307 أيام
+13030 أيام
أرشيف المشاركات
.😊

برا تست اشتراک گزاری صفحه نوشن کمک میخام یک نفر فارسی زبان کسی هست بیاد دایرکت کانال

Best Harness for Security Testing @gitbook_s/#harness

@gitbook_s/Wordlists HowToHunt -- Step-by-step vuln hunting DefaultCreds -- Default credentials

RCE in 2026 Doesn’t Look Like RCE in 2020. Here’s What Actually Matters Now. @gitbook_s/#rce

@gitbook_s/Payload Databases XSSHunter -- Blind XSS detection interactsh -- OOB callback server

Top 43 AI Security Skills, MCP Servers & GitHub Repos Every Bug Hunter Needs @gitbook_s/#ai

photo content

When a redirect param drops your value into Location: or into client-side code like window.location = params.get('next'), you don't just control a destination — you potentially control a scheme. And javascript:alert(document.domain) is a perfectly valid URL scheme as far as a browser is concerned.

Why open redirect + XSS live in the same house Most hunters treat these as two separate bugs. That's the mistake. An open redirect is you controlling where the browser goes next. XSS is you controlling what the browser executes. The bridge between them is the humble javascript: URI scheme.

Open redirect = "I control the URL." If I control the URL, I might control the scheme. If I control the scheme, javascript: = XSS.

The WAF Blocked My XSS — So I Rotated What It Was Reading @gitbook_s/#xss