The OWASP Top 10
the web's most common ways to get hacked, in plain language
The OWASP Top 10 is an awareness list from the Open Worldwide Application Security Project of the most critical risks to web applications. It is updated every few years from real data, and many standards and audits refer to it. It is a starting point, not a complete checklist.[1]
The 2025 edition, in plain words
- Broken access control: users can do or see things they should not, such as other people's records or admin functions.
- Security misconfiguration: unsafe defaults, open cloud storage, verbose errors, unnecessary features switched on.
- Software supply chain failures: risk from the components, dependencies, build tools and update channels you rely on.
- Cryptographic failures: weak or missing encryption, bad key handling, sensitive data exposed.
- Injection: untrusted input is treated as commands, as in SQL injection and cross-site scripting.
- Insecure design: flaws in the design itself that no amount of clean code fixes, such as having no limit on password guesses.
- Authentication failures: weak login, session and password handling.
- Software or data integrity failures: trusting code or data without verifying it, such as unsigned updates or unsafe deserialization.
- Security logging and alerting failures: attacks cannot be detected or investigated because the right events are not recorded or acted on.
- Mishandling of exceptional conditions: errors and unexpected situations handled in ways that expose data or fail unsafely.[2]
Earlier editions (for example 2021) grouped and ordered things a little differently, so check which edition a document refers to.
How to use it
- As a vocabulary: it gives developers, testers and managers a common language for flaws.
- As a training map: one category per week is a good team study plan.
- As a minimum, not a ceiling: passing a Top 10 scan does not mean an application is secure.
Defenses that cover many items at once
Enforce access checks on the server for every request, keep a short and current list of dependencies, use framework protections instead of hand-rolled code, validate input and encode output, harden configuration and automate it, log security events and watch them, and build security review into design and not only testing.
OWASP publishes separate lists for APIs, mobile apps and other areas. The API list is covered in its own article here.
Sources
Test yourself
My notes
Private — saved only on this device, never sent anywhere.