Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Broken Access Control?

Broken access control is a vulnerability class in which an application fails to enforce what a user may see or do, exposing other people’s data or administrative functions.

Illustration for the cybersecurity term Broken Access Control
Home / Blog / Cybersecurity Terms / What Is Broken Access Control?
17 November 2026

What Is Broken Access Control?

What Is Broken Access Control?

Broken access control is a class of vulnerability in which an application fails to enforce what a user is allowed to see or do. The result is that someone can read another customer’s records, change data they do not own, or call administrative functions they should never reach. It leads the OWASP Top 10—first in the 2021 edition and again in 2025—because it is common, damaging, and often exploitable with nothing more than an edited URL.

Why It Leads the OWASP Top 10

When OWASP rebuilt its list in 2021, broken access control climbed from fifth place to first. OWASP reported that 94% of the applications in its dataset showed some form of the weakness, and the category maps to 34 Common Weakness Enumerations, among them CWE-284 (improper access control), CWE-639 (bypassing authorisation through a user-controlled key), and CWE-22 (path traversal). The 2025 edition kept it at number one and folded server-side request forgery into the same category.

The underlying problem is almost always the same: the server trusts the client. Authentication tells the application who is making the request; access control decides whether that person may perform this action on this object. If the second check is missing, inconsistent, or performed only in the browser, the first one offers little protection. We cover the distinction in more detail in authentication and authorisation.

What It Looks Like in Practice

In APIs, the same flaws appear as Broken Object Level Authorization (API1) and Broken Function Level Authorization (API5) in the OWASP API Security Top 10 2023.

A Real-World Example

In May 2019, the US title insurer First American Financial Corporation was found to have exposed roughly 885 million records—mortgage documents containing bank account details, tax records, and Social Security numbers. Each document sat behind a URL with a sequential number, and no authentication or ownership check stood in the way. Anyone with one valid link could read the rest by incrementing a digit. It is a textbook IDOR, and a reminder that access control failures rarely need sophisticated tooling.

How to Prevent It

  1. Enforce every decision on the server. Hiding links and buttons is a usability choice, not a security control.
  2. Deny by default. A resource should be inaccessible unless a rule explicitly grants access, so a forgotten check fails safe.
  3. Centralise the logic. One well-tested authorisation layer is far easier to review than checks scattered across hundreds of controllers.
  4. Check ownership on every object access, not only at login. Unpredictable identifiers such as UUIDs make enumeration harder but are not a fix on their own.
  5. Choose a clear model. Role-based access control suits most business applications; attribute-based or relationship-based models help where rules depend on context, and policy engines such as Open Policy Agent keep those rules auditable.
  6. Log and alert on failures, invalidate sessions on the server at logout, and keep tokens short-lived.

Applying the principle of least privilege to roles from the start also limits how far a single flaw can reach.

How Testers Find It

Automated scanners struggle here because they do not understand business rules: they cannot know that user A should never see user B’s order. Effective testing uses at least two accounts per role and replays each request with the other user’s session, or with a lower-privileged one. Burp Suite extensions such as Autorize and AuthMatrix speed this up, but the judgement remains manual. Testers also try horizontal moves (same role, different tenant or customer) and vertical moves (standard user to administrator).

Regulatory Consequences in the UK

Where personal data is exposed, UK GDPR Articles 5(1)(f) and 32 require appropriate technical measures, and a breach that is likely to put individuals at risk must be reported to the ICO within 72 hours. For card environments, PCI DSS v4.0 Requirement 7 restricts access to cardholder data by business need to know. Our web application security testing checks each role and object path systematically, so these gaps are found before an attacker or a regulator finds them.

FAQ – Frequently Asked Questions

What Is the Difference Between Broken Access Control and Broken Authentication?

Broken authentication means the application cannot reliably confirm who you are, for example because of weak password handling or session flaws. Broken access control means it knows who you are but fails to limit what you can do. An attacker can be fully and correctly logged in as an ordinary user and still read other customers’ data if the authorisation checks are missing.

Can an Automated Scanner Detect Broken Access Control?

Only partially. Scanners can spot forced browsing to unprotected pages, directory listing, or obvious CORS mistakes, but they cannot tell whether a specific user should see a specific record. Most serious findings come from manual testing with several accounts across different roles, comparing what each one can reach.

Do Random IDs Fix IDOR Vulnerabilities?

No. Replacing sequential numbers with UUIDs makes guessing harder, but identifiers leak through logs, shared links, browser history, and other API responses. The real fix is a server-side check that the requesting user owns or is entitled to the object on every request. Random identifiers are a useful extra layer, not a substitute.

Is a Broken Access Control Flaw a Reportable Data Breach?

It becomes one if personal data was actually accessed or disclosed without authorisation. Under UK GDPR you must notify the ICO within 72 hours of becoming aware of a breach that is likely to risk individuals’ rights and freedoms, and inform affected people directly when that risk is high. Logs showing who accessed what are essential for this assessment.

Related Terms

You May Be Interested In These

What Is Software Composition Analysis?

Cybersecurity Terms

17 November 2026

What Is Software Composition Analysis?

Read More
What Is ATM Jackpotting?

Cybersecurity Terms

17 November 2026

What Is ATM Jackpotting?

Read More
What Is Third-Party Risk Management?

Cybersecurity Terms

17 November 2026

What Is Third-Party Risk Management?

Read More