Skip to content
Tutorials Center
My learning

Topics

Lesson 1 of 38 ยท Getting Started

What Is the OWASP Top 10?

Learn what the OWASP Top 10 is, who writes it, how the categories are chosen, how the 2021 and 2025 lists differ, and how developers should use it in real projects.

The OWASP Top 10 is a short, regularly updated list of the most critical security risks to web applications. OWASP, the Open Worldwide Application Security Project, is a nonprofit community that publishes free guides, tools and standards. Nobody owns the list: it is built from data that security companies and bug bounty programs contribute, plus a survey of practitioners who tell the editors about risks the data cannot show yet.

The list is an awareness document, not a complete checklist. It tells a team where to look first. A team that has never thought about security can use it as a starting map, and a team with a mature program can use it as a shared vocabulary: when someone says "that is an A01", everybody knows the problem is about access control.

This track walks through every category with the same rhythm: how the flaw looks in code, how an attacker (in a lab you own) sees it, and how you fix and test it. Every program in this track is a defensive stand-in that runs safely inside your browser. You never aim anything at a real site.

How the list is built

Each edition follows a similar process:

  1. Security vendors and bug bounty platforms send anonymised data: how many applications contained each type of weakness (CWE, the Common Weakness Enumeration).
  2. The editors group the weaknesses into risk categories, ranking them by how often they occur and how severe they usually are (exploitability and impact).
  3. A community survey promotes a few categories that data lags behind on, because new problems take years to show up in test results.
  4. The draft is published for comment and then finalised.

The ranking is about incidence in tested applications, not about which attack makes the news. That is why "Broken Access Control" tops the list even though injection sounds scarier: most applications have at least one access control hole.

The categories at a glance

The 2021 edition is the one most courses, audits and compliance documents still cite, and this track follows its structure. The 2025 update keeps the same spirit but regroups some items, so both are shown here.

2021 id Name One-line meaning
A01 Broken Access Control Users can act outside their permissions
A02 Cryptographic Failures Sensitive data is not protected properly
A03 Injection Untrusted input is run as code or a query
A04 Insecure Design The design lacks security controls
A05 Security Misconfiguration Unsafe defaults, open services, verbose errors
A06 Vulnerable and Outdated Components Known-vulnerable libraries stay in use
A07 Identification and Authentication Failures Weak login, session or password handling
A08 Software and Data Integrity Failures Unsigned updates, unsafe deserialization
A09 Security Logging and Monitoring Failures Attacks go unseen
A10 Server-Side Request Forgery The server fetches attacker-chosen URLs

In the 2025 edition, SSRF is folded into broken access control, security misconfiguration moves up, "software supply chain failures" widens the old components category, and a new category covers mishandling of exceptional conditions (errors that fail open). The underlying lessons are identical, so learning the 2021 list prepares you for the new one.

Python The Top 10 as data

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Grouping by theme shows something useful: only a few categories are fixed by "writing better code" alone. Design, operations and detection need decisions that happen before and after the code.

What the list is not

  • Not a standard you can pass. Saying "we are OWASP Top 10 compliant" is meaningless. For a measurable target, use the OWASP ASVS (Application Security Verification Standard), which lists testable requirements at three levels.
  • Not only about web pages. The same risks apply to APIs, mobile back ends and microservices. OWASP also publishes separate Top 10 lists for APIs, mobile apps and large language model applications.
  • Not a ranking of attackers' favourite tricks. It reflects what is found in real applications.
  • Not exhaustive. Plenty of real problems (race conditions, denial of service, clickjacking) sit outside the ten or inside several of them.

Risk, not just vulnerability

A vulnerability is a weakness. A risk combines the weakness with how likely it is to be exploited and what it would cost. A missing security header on a static page is a vulnerability with tiny risk. A missing ownership check on an invoice download is the same size of code mistake with huge risk, because it exposes customer data.

Python A tiny risk calculator

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The numbers are invented, but the habit is real: rank findings by likelihood times impact, then fix from the top. Frameworks such as the OWASP Risk Rating Methodology and CVSS formalise the same idea.

How to use the Top 10 in a project

  1. Teach it. Give every developer the list during onboarding.
  2. Map it to your stack. For each category, write down where it could occur in your application (login page, file upload, admin panel) and which framework feature protects you.
  3. Add it to code review. A review checklist with ten lines catches more than none.
  4. Test for it. The testing chapters later in the track map unit tests, static analysis and dynamic scans to categories.
  5. Watch it change. When a new edition appears, compare it to the previous one and see what moved.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the OWASP Top 10 best described as?

    It is an awareness document built from real data. It is a starting point, not a compliance badge or an exhaustive catalogue.
  2. 2. Why is Broken Access Control ranked above Injection in the 2021 list?

    Ranking reflects how common the category is in tested applications together with typical severity, not how dramatic the attack sounds.
  3. 3. Which OWASP project gives you testable requirements to verify against?

    ASVS, the Application Security Verification Standard, lists verifiable requirements at three levels. The Top 10 is for awareness.
  4. 4. A flaw is easy to exploit and exposes customer records. How should it be ranked?

    Risk is likelihood times impact. A tiny code mistake can still be a top-priority risk when the impact is large.

Summary

  • The OWASP Top 10 is a community-built, data-driven awareness list of critical web application risks.
  • Categories are ranked by how often they appear and how severe they are, not by how famous the attack is.
  • The 2021 list (A01 to A10) is the structure of this track; the 2025 update regroups it without changing the lessons.
  • It is not a compliance standard: use ASVS for verifiable requirements.
  • Rank problems by risk (likelihood times impact) and use the list in onboarding, design, review and testing.

Next: Threat Modeling and Security Thinking