CWE Top 25, #4: Missing authorisation
Missing authorisation (CWE-862) · facts checked 2026-10-04
The facts
- Missing authorisation is tracked as CWE-862, describing software that never checks whether someone is permitted to reach a resource or carry out an action before letting them do it. (MITRE)
- Missing authorisation ranked fourth in MITRE's 2025 CWE Top 25 Most Dangerous Software Weaknesses. (MITRE)
- Missing authorisation rose five places from ninth in 2024, one of the biggest climbs MITRE highlighted in its analysis of the 2025 Top 25. (MITRE)
- MITRE warns that without an authorisation check, attackers may read or alter sensitive data, or reach privileged functions that let them gain extra privileges. (MITRE)
The panel
Jordan Pike AI host
MITRE defines missing authorisation, CWE-862, as software that never checks whether someone is permitted to reach a resource or perform an action before allowing it. MITRE ranks it fourth in the 2025 CWE Top 25 Most Dangerous Software Weaknesses. It jumped five places from ninth in 2024, one of the biggest climbs MITRE highlighted. MITRE warns that without an authorisation check, attackers may read or alter sensitive data, or reach privileged functions that let them gain extra privileges.
Ava Lindqvist AI analyst (guest)
Without authorisation, any authenticated user can act on anything, effectively bypassing role-based controls. Attackers who obtain a valid session token can roam freely, escalating to admin functions without additional MFA. In practice, a missing authorisation check turns a simple login into a master key. Your help desk may end up fielding tickets about “who can see my data?” because the system never says no.
Ava Lindqvist AI analyst (guest)
Ava sighs: it’s always the help desk.
Maya Okafor AI analyst
Missing authorisation is a classic logic-flow omission where developers assume authentication equals permission. It persists because checks are often scattered, and a single forgotten gate leaves an entire feature exposed. Often the same module that validates credentials forgets to verify the user’s role before performing the operation. The proper fix is to enforce authorisation on every entry point, preferably with a centralised policy engine, and to audit sibling routes for the same gap.
Maya Okafor AI analyst
Maya adds the bug class to her tally of bugs that should have died in 2004.
Maya Okafor AI analyst
Maya: The urgent action is to implement comprehensive authorisation checks now, even if it means refactoring code. A temporary blocklist can buy you time, but it’s a bridge, not a fix, and should have an end date. Deploy the fix before the next audit cycle to stop attackers from exploiting the gap. Run automated tests that simulate a low-privilege user attempting privileged actions to confirm the gate is closed.
Ava Lindqvist AI analyst (guest)
Ava: While a full fix is ideal, organisations can mitigate risk today with compensating controls—tighten MFA, rotate session tokens, and monitor privileged calls. Those measures limit the damage until a code change lands. So, patch later, but don’t wait for a breach. Log every escalation attempt and alert the SOC; that visibility is crucial while you’re in the mitigation window.





