The "OWASP Top 10" is the common language for talking about web-app security. Here's what each item in the current 2025 edition means, framed as a lens for defense rather than attack steps, linked to this site's deeper explainers.
Read as a list of attack techniques
It becomes material to memorise, and never reaches your own application
Read as categories of risk
It tells you where to look, and becomes a starting point for prioritising
The ten risks at a glance (2025 edition)
Each item is a category. Apply them to your own app as audit points, from the top down.
| # | Risk | Roughly what it means | Related on this site |
|---|---|---|---|
| A01 | Broken Access Control | "logged in = allowed"; missing owner checks; now includes SSRF | authn vs authz / IDOR / SSRF |
| A02 | Security Misconfiguration | prod debug, defaults, exposed features | CORS / .env |
| A03 | Software Supply Chain Failures | ignored known CVEs in dependencies, plus tampered build and distribution paths | monitoring dependency CVEs |
| A04 | Cryptographic Failures | secrets in plaintext, weak crypto, TLS gaps | public-key crypto / password hashing |
| A05 | Injection | input hijacks a query/command | SQL injection / XSS |
| A06 | Insecure Design | threats not considered at design time | the minimum checklist |
| A07 | Authentication Failures | weak auth, no brute-force resistance, no MFA | 2FA / passkeys |
| A08 | Software or Data Integrity Failures | unsigned or unverified updates; trusting data without checks | history of security (supply chain) |
| A09 | Security Logging and Alerting Failures | can't detect or trace an incident; logs nobody is alerted on | why audit logs matter |
| A10 | Mishandling of Exceptional Conditions | requests go through when an error occurs; error pages reveal internals | the minimum checklist |
What changed from the 2021 edition
| 2021 | 2025 | Change |
|---|---|---|
| A01 Broken Access Control | A01 Broken Access Control | Still first; absorbs SSRF (A10:2021) |
| A05 Security Misconfiguration | A02 Security Misconfiguration | Up from 5th to 2nd |
| A06 Vulnerable and Outdated Components | A03 Software Supply Chain Failures | Widened from known vulnerabilities to the whole supply chain |
| A02 Cryptographic Failures | A04 Cryptographic Failures | Down from 2nd to 4th |
| A03 Injection | A05 Injection | Down from 3rd to 5th |
| A04 Insecure Design | A06 Insecure Design | Down from 4th to 6th |
| A07 Identification and Authentication Failures | A07 Authentication Failures | Shorter name |
| A08 Software and Data Integrity Failures | A08 Software or Data Integrity Failures | Same rank |
| A09 Security Logging and Monitoring Failures | A09 Security Logging and Alerting Failures | Emphasis on alerting and acting, not only recording |
| A10 Server-Side Request Forgery (SSRF) | A10 Mishandling of Exceptional Conditions | New category |
The 2025 edition draws on testing data from about 2.8 million applications contributed by 13 organizations, plus a community survey. Software Supply Chain Failures was ranked first by exactly half of the survey respondents.
How it differs from similar names
| Name | What it is | Main use |
|---|---|---|
| OWASP Top 10 | The most critical web-app risks grouped into ten categories | Prioritization, training, a shared vocabulary |
| OWASP ASVS | A detailed verification standard of web-app security requirements (about 350 in 5.0, three levels) | Writing requirements, scoping assessments and contracts |
| CWE | MITRE's catalog of software weakness types | Classifying root causes; each Top 10 item groups several CWEs |
| CVE | An ID for a specific vulnerability in a specific product | Checking whether a product you use is affected |
Real cases
Top 10 items also work as a way to classify the causes of real incidents. Mapping cases covered on this site:
- A01 Broken Access Control: the UK Companies House WebFiling flaw (signed-in users could see other companies' non-public information). SSRF, the cause of the Capital One breach (2019), also sits here in the 2025 edition
- A03 Software Supply Chain Failures: the Equifax breach (2017) came from a component that had not been updated although a fix was available. The Trivy supply-chain compromise (2026) targeted the distribution path of a developer tool
- A07 Authentication Failures: the 7pay fraud (2019), where a payment app without two-step verification was taken over
How to check your own app
A01: try to reach someone else's data
Create two test accounts. Signed in as A, request B's order or profile by its ID (the number in the URL or API call) and confirm it is refused. Also confirm a regular account can't reach admin screens or APIs.
A02: check public settings mechanically
Check headers with the Security Headers Check. For a site you've verified you own, the Site Security Audit covers exposed .env and .git files, CORS and cookie flags in one pass.
A03: look at dependencies and the build path
Check your lockfile for known vulnerabilities with the Dependency Vulnerability Scanner. Pin the versions of tools and actions used in CI, and limit who can publish releases.
A09 and A10: check errors and logs
Trigger errors with a missing page or invalid input and confirm no stack traces, SQL statements or other internals appear. Confirm failed logins and permission errors are logged, and that someone is notified when they keep happening.
How to use it: a prioritization start, not a checklist
Don't treat 'covering' the Top 10 as done
The Top 10 is the ten most representative categories, not a guarantee of sufficiency. Use it as a starting point for prioritization and gap-finding, and also cover the basics it doesn't directly address: secret management, backups, and detection.
Start at the top (A01–A03) in your own app
Audit access control, configuration, and dependencies first; the most frequent incident sources cluster here.
Check config and dependencies (A02, A03) mechanically
Tighten production config (no debug exposure) and make dependency CVE monitoring a mechanism.
Have detection (A09) before an incident
Without logs and alerts you can't notice or trace an incident. Retain at least basic audit and access logs, and make sure someone is notified when something looks wrong.
This site's view: a tool for mapping onto your own code
The value of the Top 10 isn't memorizing numbers; it's mapping each category onto your own app and auditing it. This site keeps per-risk explainers translated into "how you defend." Use the Top 10 as a starting point, and start with the top items (access control, configuration, dependencies) in your own app.
Read next
- Basics: authentication vs authorization (the heart of A01) · the minimum security checklist
- Glossary: SQL injection · IDOR · SSRF
- History: the history of security (timeline)
Sources
- OWASP Top 10:2025 (official): top10.owasp.org
- OWASP Top 10:2025 — Introduction (changes from 2021 and data): top10.owasp.org
- OWASP Top 10:2021 (official): owasp.org
- OWASP Application Security Verification Standard (ASVS): owasp.org