CWE Top 25, #24: Authorisation bypass via user key
User-controlled key bypass (CWE-639) · facts checked 2026-10-04
The facts
- CWE-639 covers authorisation that fails to stop a user from reaching someone else's records just by altering the identifier used to look them up. (MITRE)
- Authorisation bypass through a user-controlled key ranked twenty-fourth in MITRE's 2025 CWE Top 25 Most Dangerous Software Weaknesses, up six places from thirtieth in 2024. (MITRE)
- MITRE notes overlap between this weakness and the terms insecure direct object reference, or IDOR, and broken object level authorisation, or BOLA. (MITRE)
- In July 2023, Australia's ACSC, CISA and the NSA jointly warned that IDOR flaws are common, can be abused at scale and are frequently exploited in data breaches. (CISA)
The panel
Jordan Pike AI host
MITRE says CWE-639 covers authorisation that fails to stop a user from reaching someone else's records just by altering the identifier used to look them up. MITRE also notes overlap between this weakness and the terms insecure direct object reference, or IDOR, and broken object level authorisation, or BOLA.
Jordan Pike AI host
MITRE ranks authorisation bypass through a user-controlled key twenty-fourth in its 2025 CWE Top 25 Most Dangerous Software Weaknesses, up six places from thirtieth in 2024. And in July 2023, Australia's ACSC, CISA and the NSA jointly warned that IDOR flaws are common, can be abused at scale and are frequently exploited in data breaches.
Jordan Pike AI host
If your company runs any app where customers log in and see their own records, this one is for you. Dex, how does an attacker see it?
Dex Moreno AI analyst
Getting in is the dull part. The attacker is typically just a normal user with an ordinary account. They notice the app looks up a record using a value they can see and change, and they ask whether the app checks who is asking. If it doesn't, the foothold is other people's records, one after another. From there it can lead downstream: contact details and account data are good fuel for phishing and account takeover, and that's why the joint warning stressed abuse at scale.
Dex Moreno AI analyst
Elegance score: eight out of ten. It's the technique equivalent of trying a door handle to see if it's locked. The application deserved better.
Jordan Pike AI host
Dex, we are not rating it out of ten.
Maya Okafor AI analyst
The bug class is a missing ownership check. The app confirms who you are, which is authentication, but never confirms that you may touch this particular record, which is authorisation. It keeps happening because developers check at the front door, the menu or the page, and forget the data layer behind it. A complete fix is a server-side check on every request, for every route that reads, changes, deletes or exports a record, asking whether this caller is allowed this specific object.
Maya Okafor AI analyst
Adding it to the tally of bugs that should have died in two thousand four. It's still here, and it moved up six places.
Dex Moreno AI analyst
Counterpoint: unpredictable record keys do slow down an attacker who is guessing. Not a cure, but it makes bulk harvesting noisier. And noise is something defenders can catch. One account requesting a long run of different records is a pattern worth alerting on, and the signs usually show up before the breach is noticed.
Maya Okafor AI analyst
Fine as a bridge, but a bridge needs an end date. Hard-to-guess keys leak through shared links, logs and browser history, and then you're relying on secrecy instead of authorisation. The real fix is the check. Then hunt for siblings: if one route skips the check, the neighbouring routes for update, delete and export probably do too. Also check that the check isn't only on the page that displays the record.
Jordan Pike AI host
So: Monday morning?
Dex Moreno AI analyst
Test your own app as a normal user: log in with two accounts and see whether one can reach the other's records. Then turn on alerting for accounts pulling an odd spread of records.
Maya Okafor AI analyst
Make the ownership check a shared, central piece of code rather than something each developer remembers. Then write tests that fail when a route skips it, and ask your vendors the same question about their software.





