@kikomanasijev@StanleyMasinde_@laravel@taylorotwell And can you explain this PHP just got a critical vulnerability
https://t.co/leFEZL16SH
Image both Laravel and PHP having a very critical vulnerability in the same week putting big site in big danger.
@Creed0C From a random 500 error → full read + write on other users’ data because the backend just yeeted the WHERE clause when it saw an unknown filter. That’s the kind of “wait… what?” finding that makes bug bounty addictive.
@StanleyMasinde_@kikomanasijev@laravel@taylorotwell I’m referring to the Node.js ecosystem, its libraries, and frameworks, which I believe offer better security architecture than PHP and Laravel in certain areas.
I found a Critical Account Takeover on Headway trading platform.
One malicious link = full access to any user’s account.
No password. No 2FA needed.
I responsibly submitted it to Headway and got paid $50 for the bug.
Video of how I did it below 👇
#bugbounty#cybersecurity
I found a Critical Account Takeover on Headway trading platform.
One malicious link = full access to any user’s account.
No password. No 2FA needed.
I responsibly submitted it to Headway and got paid $50 for the bug.
Video of how I did it below 👇
#bugbounty#cybersecurity
I found a Critical Account Takeover on Headway trading platform.
One malicious link = full access to any user’s account.
No password. No 2FA needed.
I responsibly submitted it to Headway and got paid $50 for the bug.
Video of how I did it below 👇
@0xPrayers Nice escalation 🔥 Blind → full read via the PDF renderer is always satisfying.
Fuzzing the render pipeline for the win. That control plane debug page in the PDF is a clean hit.
@codewithbdr@immunefi@codewithbdr complains about paying a $75 submission fee on Immunefi only to have the report closed as a duplicate of a valid existing report, with no upfront mechanism to check for duplicates.
@0xPrayers Nice escalation 🔥 Blind → full read via the PDF renderer is always satisfying.
Fuzzing the render pipeline for the win. That control plane debug page in the PDF is a clean hit.
@Creed0C From a random 500 error → full read + write on other users’ data because the backend just yeeted the WHERE clause when it saw an unknown filter. That’s the kind of “wait… what?” finding that makes bug bounty addictive.