Filter
Exclude
Time range
-
Near
AI-generated code produces up to 2.7× more vulnerabilities than human-written code, often missing the auth checks your app needs 🎭 That's a real problem for #BrokenAccessControl, the No. 1 risk on the OWASP Top 10 since 2021. Catch it before it ships 🔗 blog.secureflag.com/2026/06/…
6
Hunters spend hours on subdomain enumeration before opening the actual app. The bugs that pay live on the app you haven't opened yet. In this video, I show the exact recon process I use on every new target. No tool chain. Just the application, my proxy, and a way of reading what I see that pulls bugs out on almost every program. How I Do Recon in 2026? youtu.be/H7AjEMqcXNY #BugBounty #Recon #WebSecurity #EthicalHacking #AmrSec #BrokenAccessControl
15
119
7,243
Com o Burp Repeater, basta falsificar esse header trocar o cookie da sessão para escalar privilégios sem ser admin de verdade. Acredito que seja mais uma forma clássica de Broken Acess Control. Constância > tudo. #BugBounty #Jornada229Dias #BrokenAccessControl
5
194
Dia 1 foi concluído, hoje inicia o dia 2 Foco é entrar no entendimento de XX com força! #BugBounty #BugHunter #PortSwigger #BrokenAccessControl #Jornada229Dias #bolhasec
1
8
584
The #IDOR That "Isn't" a Vulnerability… Yet Many IDOR findings are dismissed with a simple argument: "No unauthorized data is exposed". Technically, that may be true today. But security isn’t about the present moment, it's about what happens when the code inevitably changes. --- What IDOR Really Exposes Insecure Direct Object Reference occurs when applications rely on user-controllable identifiers like user_id=101 in URLs or API requests without enforcing strict authorization checks. Attackers simply modify the identifier. user_id=101 → user_id=102 If the application trusts that input without validating ownership, the attacker can access or modify another user's data. This is classic horizontal privilege escalation. But here's the nuance: sometimes the access control currently blocks it. Developers see that and conclude the issue is harmless. --- ⚠️ Future Code Changes A "potential IDOR" is often a #design flaw waiting for the wrong commit. #Security logic evolves. APIs get refactored. New features reuse endpoints. The moment a #developer removes or weakens a check, intentionally or not, that latent flaw becomes a #critical Broken Access Control (#BAC) vulnerability. This is why experienced penetration testers flag it early. Not because it is exploitable today. Because the architecture allows it to become exploitable tomorrow. --- How to #Eliminate the Risk The safest approach is architectural: - Enforce server-side authorization checks for every object request. - Validate that the user owns or is authorized for the resource. - Avoid exposing direct database identifiers. - Use indirect references such as GUIDs. Security should never depend on developers remembering to add checks everywhere. It should be built into the design. - logisek.com #CyberSecurity #PenTest #RedTeam #InfoSec #OffSec #BrokenAccessControl #SecurityMindset #OffensiveSecurity #Logisek
1
1
204
Nueva charla: Detectando Broken Access Control con Autorize (Burp Suite) @JoacoarenaOk Aprendé a identificar IDOR y BAC en escenarios reales usando Autorize para automatizar pruebas de autorización y detectar accesos indebidos entre usuarios. 👉 Mirala acá: youtu.be/TBzgZw80M1o #BurpSuite #BugBounty #BrokenAccessControl
2
7
721
Should I be seeing this? 🔐 New talk: Detecting Broken Access Control with Autorize (Burp Suite) @JoacoarenaOk Learn how to identify IDOR and BAC in real-world scenarios using Autorize to automate authorization testing and uncover improper access between users. 👉 Watch it here: youtu.be/TBzgZw80M1o @PortSwigger #BurpSuite #BugBounty #BrokenAccessControl
2
9
736
HTTP methods don't provide security. Relying on GET vs POST for access control leads to broken authorization - proper checks must always be enforced server-side. #AppSec #BrokenAccessControl #WebSecurity
43