Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
The OWASP Top 10 is a widely recognised awareness document that ranks the most critical security risks facing web applications, based on real-world data and community input.

What Is the OWASP Top 10?
The OWASP Top 10 is a regularly updated list of the most critical security risks to web applications, published by the Open Worldwide Application Security Project (OWASP), a not-for-profit foundation. It is built from vulnerability data contributed by testing firms and organisations, combined with a community survey, and it has become the most widely referenced starting point for web application security.
The list is an awareness document rather than a complete standard. It tells developers, testers, and managers where the most common and damaging problems lie, but a secure application needs to go well beyond these ten categories.
The 2021 edition, still widely used in contracts and training material, contains the following categories:
| Rank | Category |
|---|---|
| A01 | Broken Access Control |
| A02 | Cryptographic Failures |
| A03 | Injection |
| A04 | Insecure Design |
| A05 | Security Misconfiguration |
| A06 | Vulnerable and Outdated Components |
| A07 | Identification and Authentication Failures |
| A08 | Software and Data Integrity Failures |
| A09 | Security Logging and Monitoring Failures |
| A10 | Server-Side Request Forgery (SSRF) |
The 2025 edition keeps Broken Access Control at number one, moves Security Misconfiguration up the list, and introduces categories for software supply chain failures and the mishandling of exceptional conditions. The underlying lessons, however, remain much the same.
Broken access control covers any situation where users can act outside their intended permissions, such as changing an ID in a URL to view another customer’s invoice (an insecure direct object reference). It has topped the list since 2021 because it is common and often serious.
Injection includes SQL injection, command injection, and cross-site scripting. It happens when untrusted input is interpreted as code or commands.
Cryptographic failures expose sensitive data through weak or missing encryption, outdated algorithms, or poor key management.
Insecure design recognises that some flaws cannot be fixed with better code because the design itself is wrong, for example a password reset flow that relies on easily guessed security questions. Threat modelling during design is the best defence.
Vulnerable and outdated components reflects how much modern software depends on third-party libraries. The Log4Shell vulnerability (CVE-2021-44228) in December 2021 showed how a single library flaw can affect thousands of applications at once.
Server-side request forgery lets an attacker make the server send requests on their behalf, often to internal services or cloud metadata endpoints that should never be reachable from outside.
For developers, the list is a practical training curriculum. Each category comes with prevention guidance, and OWASP’s Cheat Sheet Series gives detailed advice on topics such as input validation and session management.
For security teams, it offers a baseline for code reviews, automated scanning, and penetration testing scopes. It is also useful when writing secure coding requirements for suppliers.
For managers, it provides a simple framework for discussing application risk and tracking improvement over time.
What it should not become is a checklist that marks an application as “secure” once ten boxes are ticked. For a more thorough set of requirements, OWASP publishes the Application Security Verification Standard (ASVS), which defines testable controls at three levels of assurance.
OWASP maintains several specialised Top 10 lists, including the API Security Top 10, the Mobile Top 10 (relevant to mobile application security), and the Top 10 for Large Language Model Applications, which covers risks such as prompt injection.
Fixing vulnerabilities in code is always the priority, ideally as part of secure software development. A web application firewall can add a protective layer and buy time while fixes are developed, but it does not replace secure code.
At Privia Security, our Web Application Security Services test your applications against the OWASP Top 10 and well beyond, with clear guidance for your developers.
OWASP has historically released a new edition every three to four years, with versions in 2003, 2004, 2007, 2010, 2013, 2017, 2021, and 2025. Each update is based on fresh vulnerability data and community input, so categories are merged, renamed, or reordered to reflect how real applications are being attacked at the time.
Not formally, but it is frequently referenced by standards and contracts. PCI DSS, for example, expects developers to be trained in common coding vulnerabilities, and many customers ask suppliers to show that their applications have been tested against the Top 10. For detailed, testable requirements, OWASP recommends the Application Security Verification Standard instead.
A WAF can block many attacks associated with injection and some other categories, but it cannot fix broken access control, insecure design, or business logic flaws, because those requests often look perfectly legitimate. A WAF is a valuable extra layer, not a substitute for secure development and regular application testing.
Yes, a web application penetration test should always cover the Top 10 categories, but a good test goes further. It should also examine business logic, authorisation across user roles, API endpoints, and the specific risks of your application, because many serious vulnerabilities fall outside any generic list.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.