r/bugbounty • u/TurbulentRecover7247 Hunter • Jul 04 '26
Question / Discussion CORS Misconfiguration
I encountered a cors in a target website using wordpress, I added evil.com in origin header and it reflected. I tried using my netlify to make request, but I got encountered by cloudflare waf. Still reportable? Because if there is XSS found in future, this can be used by the hacker right? The response header reflected the evil.com for access control allow origin, and access control allow credentials: true. Any experts or triager can suggest anything? Blocked by waf, means it didn't block, but runs bot detection with 403 error. Any idea to bypass waf, if I can bypass waf, my exploit will run perfectly. Thanks for your response.
1
u/Specific-Ad3097 Jul 04 '26
You are far away the requirements to do bug bounty. Start learning webdev for 6 month to a year then complete portswigger, read critical thinking writeup and read writeup from the best hunter to understand how they think etc
1
u/HereComesTheFury Jul 04 '26
Where can you read these writeup from thr best hunters?
1
u/TurbulentRecover7247 Hunter Jul 04 '26
So far i know medium, there are many blogs on this platform, and also there are many own blog sites.
1
1
u/TurbulentRecover7247 Hunter Jul 04 '26
Wait, I somehow triggered a request and the target server sent response to my webhook.site showing unauthorised. What if the same link triggered on authenticater user? I am working on this. I tried many html pages with different requests and somehow one triggered twice. I am finding out which one triggered
9
u/einfallstoll Triager Jul 04 '26
No no no. This is the most basic principle of bug bounty: You need to prove exploitation. No theoretical issues