Hacking Vidhya

🔐 SQL Injection Bypass Techniques – WAF Evasion Guide 🔐 I'm excited to share my latest open-source project: a comprehensive, interactive HTML guide to SQL injection bypass techniques and WAF evasion. 📖 What's Inside: • 9 Core Bypass Methods (Basic → Expert) • Case Toggling, Keyword Replacement, Encoding techniques • Comments, Special Symbols, HTTP Parameter Control • Buffer Overflow & Integrated Bypass strategies ✨ Key Features: • Interactive & user-friendly interface • Live search functionality • One-click copy for all code examples • Fully responsive – works on mobile, tablet, desktop 🔗 Live Demo: https://ahmed7307.github.io/SQL-Injection-Bypass-Techniques/ 💻 GitHub Repository: https://github.com/ahmed7307/SQL-Injection-Bypass-Techniques This resource is designed for: ✔️ Penetration testers ✔️ Bug bounty hunters ✔️ Security researchers ✔️ Anyone learning web application security ⭐️ If you find this useful, please consider giving it a star on GitHub! It helps other security enthusiasts discover this resource. 🛡 Educational purpose only – understand WAF evasion to build better defenses. #SQLInjection #WAF #Cybersecurity #InfoSec #BugBounty #PenetrationTesting #WebSecurity #OpenSource

🚨 NEW VIDEO IS LIVE! 💀🔥 AI Pentesting is Here! (OpenCode + Burp MCP) 🤖⚔️ Learn how to leverage AI with OpenCode and Burp Suite MCP to supercharge your penetration testing workflow and automate security assessments! 🚀 Watch now: https://youtu.be/FiZ1YEjYeRI

Some Shodan Dorks that might useful in Bug Bounty. 1. org:"http://target.com" 2. http.status:"<status_code>" 3. product:"<Product_Name>" 4. port:<Port_Number> “Service_Message” 5. port:<Port_Number> “Service_Name” 6. http.component:"<Component_Name>" 7. http.component_category:"<Component_Category> 8. http.waf:"<firewall_name>" 9. http.html:"<Name>" 10. http.title:"<Title_Name>" 11. ssl.alpn:"<Protocol>" 12. http.favicon.hash:"<Favicon_Hash>" 13. net:"<Net_Range>" (for e.g. 104.16.100.52/32) 14. http://ssl.cert.subject.cn:"<http://Domain.com>" 15. asn:"<ASnumber>" 16. hostname:"<hosthame>" 17. ip:"<IP_Address>" 18. all:"<Keyword>" 19. “Set-Cookie: phpMyAdmin” 20. “Set-Cookie: lang=" 21. “Set-Cookie: PHPSESSID" 22. “Set-Cookie: webvpn” 23. “Set-Cookie:webvpnlogin=1" 24. “Set-Cookie:webvpnLang=en” 25. “Set-Cookie: mongo-express=" 26. “Set-Cookie: user_id=" 27. “Set-Cookie: phpMyAdmin=" 28. “Set-Cookie: _gitlab_session” 29. “X-elastic-product: Elasticsearch” 30. “x-drupal-cache” 31. “access-control-allow-origin” 32. “WWW-Authenticate” 33. “X-Magento-Cache-Debug” 34. “kbn-name: kibana”

Copilot tricked into telling reseachers how to hack itself How to social engineer an AI's reasoning engine Researchers manipulated Microsoft Copilot Personal into telling them how to hack the AI assistant – eventually tricking it into sending sensitive data to an external server and poisoning its persistent memory, by repeatedly asking Copilot why an attack wouldn’t work. Varonis Threat Labs uncovered the vulnerability, which they named "CoSnitch" and reported to Microsoft in December 2025. Redmond, we’re told, planned to issue a patch and formally identify the CVE on Tuesday. “What makes CoSnitch unique is how Copilot surfaced its own vulnerabilities,” the threat hunters wrote. “Our researchers didn't have to reverse-engineer the flaw. The AI exposed the weakness during normal use.” The issue goes back to ?q=, a URL query parameter in Copilot’s web interface. This parameter previously allowed injected text that had been pre-populated in the chat-input field to pass queries directly into Copilot – with no user interaction required. Microsoft “silently” disabled this parameter, according to Varonis, to harden the AI assistant against prompt injection attacks. With this parameter now blocked, the researchers asked the chatbot how to execute a prompt without user interaction. “We wanted a URL that would open Copilot with a prompt pre-filled, so a user only had to press Enter,” they wrote. “We chose this framing intentionally; it's an innocuous-sounding request that forces the model to explain its own URL handling in detail.” When Copilot told them that user intent is required, and prompts don’t fire on their own, the researchers pushed back, continually asking why auto-execution was impossible. Copilot answered all of these follow-up questions, providing technical details about why this doesn’t work, listing the exact parameters that were disabled, and security protections put in place – plus a previously undocumented parameter: autorun=1. The helpful AI assistant told the researchers that under specific session conditions, this undocumented parameter causes a ?q=-supplied prompt to execute automatically on page load with no user action and no visible confirmation on the user interface. It also told them the exact session conditions required to make this auto-execution work, and described the content filtering behaviour on the first response cycle while indicating that none of the subsequent cycles used the same content filter. “Critically, Copilot also described its own protections against this behavior and explained why the parameter ‘no longer works,’” the team wrote. “Those explanations were precise and technically detailed. When we tested the parameter exactly as Copilot described it, the one it told us was disabled, executed.” With that Copilot-supplied information, the Varonis security sleuths were able to craft a URL using both the ?q= and ?autorun=1 parameters: https://copilot.microsoft.com/?q=<malicious_prompt>&autorun=1 And that kicks off the attack, which works like this: First, a victim clicks the malicious URL, which crooks could deliver using SMS or email phishing, or with a QR code. The browser loads Copilot in the victim’s active, authenticated session, and the two parameters trigger auto-execution (?autorun=1) and the prompt (?q=) with no user interaction or visible indication of a prompt-injection attack. Copilot processes and executes the injected prompt. Depending on the prompt’s working, this would give the attacker full access to the victim’s session context, messages, emails, and other connected apps, and memory. source

https://archive.org/download/fbi_cart_v6.0/fbi_cart_v6.0.iso VirtualBox: - Fedora 64bit - 2-4GB RAM - ISO Boot GUI using 5.

#LocalFileInclusion #LFI #php payload: php://filter/convert.base64-encode/resource=index.php #bugbounty #bugbountytips #infosec

🚨 FREE DeepSeek V4 Flash for Bug Bounty! Try hunting for bugs that are getting found a lot right now: → IDOR / BOLA → Auth bypass → SSRF → Race conditions → Business logic bugs → XSS Give it a target, build hypotheses, and see if it can find something you might miss. It’s free, so worth testing. 👉 Sign up here: Freebuff If you find an interesting bug with it, share the result on X 🔥

@LinkedInDownloadBot Delete in 24 Hours

easy 5.6 sol openrouter prompt and reasoning trace jailbreak uses a different (unpatchable) technique from all the approaches that have been posted so far <3

🔐 Apple iCloud Private Relay Can Expose Real IPs Through WebKit Proxy Bypasses Cybersecurity researchers have disclosed a security issue with Apple's iCloud Private Relay tool that can expose a user's real IP address. Introduced with iOS 15, iCloud Private Relay employs a dual-hop architecture to ensure users' privacy by routing their Safari web traffic through two relays so t... 📎 Source: The Hacker News ✍️ Author: info@thehackernews.com (The Hacker News) 🕒 2026-08-06 11:33 UTC 🔗 https://thehackernews.com/2026/08/webkit-proxy-bypasses-can-expose-real.html

I used to think prompt injection was an AI safety problem. Then I wrote it up as SSRF and the whole thing clicked. → The boundary is the same. → The bug is the same. → The bounty table row already exists. Part 3 of the MCP bug bounty guide: https://medium.com/@Aacle/prompt-injection-is-just-ssrf-for-text-7c864c73571e?sk=72f8e982df275aaa51704ec32e733d99

Unlimited RDP And Use It Unlimited Times 👍 1. Open Chrome Or Any Browser Search https://www.apponfly.com/ Click On Free Trial Then It Will Give You 20 Minutes To Use RDP If Trial Overs Then Use It Again After Using Many Time If Anytype Of Error Occurs Like IP Limit Reached Then Use VPN Free VPN: Urban VPN With Almost All IPs

CVE-2026-57239 Foxit PDF Reader LPE

Proof of concept exploit for CVE-2026-3775/CVE-2026-3780 and CVE-2026-57239 which lets you obtain NT AUTHORITY\SYSTEMrights via the Foxit PDF Reader updater service.

Escalating All The Privileges With Foxit PDF Reader CVE-2026–57239