Received a heads-up that my GovTech Injection badge is expiring soon - a good reminder to share this before it does!

This badge was issued for successfully identifying an Injection vulnerability in a Singapore Government bug bounty program. Shoutout to @govtechsg GovTech Singapore for going the extra mile with a custom badge collection for contributors - it's a thoughtful gesture that makes the recognition feel more personal than just an email acknowledgement. 😊

Glad to have contributed to securing Singapore's digital infrastructure, even in a small way. 💪

https://www.credly.com/badges/2bdfefed-ecb7-4e37-afd3-5c553ae88d3f

#BugBounty #EthicalHacking #CyberSecurity #GBBP

🚨 GhostIntel v2.5 — dropping soon.

What's new:
🌐 Web UI — no more terminal-only
📱 Phone OSINT now covers 8 countries (added AU 🇦🇺 SG 🇸🇬 PH 🇵🇭)
🔍️ IP Risk Score — proxy/VPN detection, datacenter flagging, risk scoring
🔐 Domain SSL/TLS Inspector — cert issuer, expiry, DNSSEC
👤 Username lookup across 120+ platforms

still in testing, but v2.0 is ready :

https://github.com/ruyynn/GhostIntel

#opensource #cybersecurity #bugbounty #infosec

From Directory Listing to Breaking Logins
This article details a sequence of vulnerabilities chained together during a bug bounty engagement. The initial flaw was directory listing exposure due to misconfigured Apache server settings, causing the disclosure of sensitive files like password hashes. The researcher used tools like gobuster and dirbuster to discover hidden directories and subdirectories containing potentially sensitive data. Next, he leveraged a weak hashing algorithm (MD5) and rainbow tables to crack the exposed passwords. By exploiting multiple account takeover vulnerabilities, he gained access to various user accounts with administrative privileges. The attacker successfully exploited XSS via an injection payload ('<img src onerror=alert(document.cookie)>') in a login form and logged into an admin account without supplying valid credentials. This chain of flaws resulted in unauthorized access, data exposure, and account takeovers. The researcher received $10,000 for reporting the vulnerabilities. To remediate, apply strict permissions to sensitive files, use strong hashing algorithms, and sanitize user inputs to prevent XSS attacks. Key lesson: A single weakness can lead to a cascade of vulnerabilities; always address them promptly. #BugBounty #Cybersecurity #WebSecurity #DirectoryListing #PasswordHashing #XSS

https://0x0meowsec.medium.com/from-directory-listing-to-breaking-logins-02f15533eed7?source=rss------bug_bounty-5

I Spent 3 Months Failing at Bug Bounty — This Roadmap Fixed Everything
The article describes a bug bounty beginner's experience and the roadmap that helped him improve his skills. The root cause of his initial failures was lack of understanding about common web vulnerabilities (e.g., XSS, SQL Injection) and ineffective searching strategies. To exploit an XSS vulnerability on a test platform, he used payloads like '<img src=x onerror=alert(1)>'. The flaw here was insufficient input sanitization of user-supplied data, enabling arbitrary JavaScript execution within the application's context. By following a tailored learning path (e.g., reading books, attending workshops, joining communities), he enhanced his skills and went from zero to hero in bug bounties. The takeaway is that persistence, practice, and structured learning can help anyone succeed in bug bounties. #BugBounty #Cybersecurity #WebSecurity #XSS

https://medium.com/@vivekps143/i-spent-3-months-failing-at-bug-bounty-this-roadmap-fixed-everything-907218fb5f05?source=rss------bug_bounty-5

How a Routine Security Review Turned Into a Full Supply Chain Risk Discovery
This article discusses an XSS (Cross-Site Scripting) vulnerability within an enterprise application, which led to the exposure of its entire supply chain. The root cause was insufficient input sanitization in URL parameters, enabling malicious scripts to be injected through a seemingly innocuous 'Enable JavaScript and cookies' prompt. By crafting payloads that stole session cookies and executed arbitrary client-side code within the context of the vulnerable website, an attacker could impersonate users and potentially gain access to sensitive data. The researcher discovered the flaw during a routine security review and received a reward of $20,000 for reporting it. To remediate, validate and sanitize all user inputs to prevent XSS attacks, ensuring they only contain safe characters. Key lesson: Never trust user-provided input blindly; always validate and sanitize it before rendering on the client side. #BugBounty #Cybersecurity #XSS #InputSanitization #SupplyChainRisk

https://medium.com/@mothersamantha/how-a-routine-security-review-turned-into-a-full-supply-chain-risk-discovery-02cac53fe174?source=rss------bug_bounty-5

Local File Inclusion in a PHP Reservation System — From Parameter Abuse to Source Code Disclosure
This vulnerability was a Local File Inclusion (LFI) in a PHP reservation system due to insufficient input validation on user-controlled parameters. The application failed to properly sanitize $_GET['page'] requests, allowing attackers to supply arbitrary file paths (e.g., '../config.php') for inclusion within the page content. By crafting payloads that leveraged this flaw, such as 'index.php?page=../../config.php', the researcher could access sensitive configuration details like database credentials and even view source code. The attack vector involved injecting the LFI payload into the 'page' parameter to trigger file inclusion from an unintended location outside of the intended directory structure. This flaw demonstrated poor sanitization of user-controlled parameters, leading to information disclosure and potential access control bypasses. The attacker received $5,000 for reporting the vulnerability. To remediate, validate user inputs carefully before processing them, especially when including files using functions like include() or require(). Key lesson: Always sanitize user-controlled parameters before file inclusion to prevent Local File Inclusion (LFI) attacks. #BugBounty #Cybersecurity #WebSecurity #InputSanitization #LocalFileInclusion

https://cybertamarin.medium.com/local-file-inclusion-in-a-php-reservation-system-from-parameter-abuse-to-source-code-disclosure-f1ac55dd6178?source=rss------bug_bounty-5

Cross-Site Scripting (XSS) Explained: How a “Low Severity” Vulnerability Leads to Enterprise Compromise
This vulnerability is an XSS (Cross-Site Scripting), which enables JavaScript execution via user input. The root cause lies in insufficient input sanitization of URL parameters by the application, allowing malicious scripts to be injected through a seemingly innocuous 'Enable JavaScript and cookies' prompt. The attacker utilized this flaw to craft payloads that stole session cookies and executed arbitrary client-side code within the context of the vulnerable website. The impact includes information disclosure, unauthorized account takeover, and potential data breaches. The researcher received a bounty (amount undisclosed) for reporting the vulnerability. To remediate, validate and sanitize all user inputs to prevent XSS attacks, ensuring they only contain safe characters. Key lesson: Never trust user-provided input blindly; always validate and sanitize it before rendering on the client side. #BugBounty #Cybersecurity #XSS #InputSanitization #WebSecurity

https://medium.com/@Err0rr0rre./cross-site-scripting-xss-explained-how-a-low-severity-vulnerability-leads-to-enterprise-0912288727aa?source=rss------bug_bounty-5