Glossary

What is the OWASP Top 10: the standard list of the 10 biggest web-app risks

The OWASP Top 10 is the standard list of the most critical web app risks. What each 2025 category means, what changed from 2021, and what to defend first.

Published 2026-07-04 Updated 2026-10-06 8 min read
On this page

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 Top 10 is a set of risk categories, not a list of attack techniques — so use it as a review lens, not something to memorise.

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.

#RiskRoughly what it meansRelated on this site
A01Broken Access Control"logged in = allowed"; missing owner checks; now includes SSRFauthn vs authz / IDOR / SSRF
A02Security Misconfigurationprod debug, defaults, exposed featuresCORS / .env
A03Software Supply Chain Failuresignored known CVEs in dependencies, plus tampered build and distribution pathsmonitoring dependency CVEs
A04Cryptographic Failuressecrets in plaintext, weak crypto, TLS gapspublic-key crypto / password hashing
A05Injectioninput hijacks a query/commandSQL injection / XSS
A06Insecure Designthreats not considered at design timethe minimum checklist
A07Authentication Failuresweak auth, no brute-force resistance, no MFA2FA / passkeys
A08Software or Data Integrity Failuresunsigned or unverified updates; trusting data without checkshistory of security (supply chain)
A09Security Logging and Alerting Failurescan't detect or trace an incident; logs nobody is alerted onwhy audit logs matter
A10Mishandling of Exceptional Conditionsrequests go through when an error occurs; error pages reveal internalsthe minimum checklist

What changed from the 2021 edition

20212025Change
A01 Broken Access ControlA01 Broken Access ControlStill first; absorbs SSRF (A10:2021)
A05 Security MisconfigurationA02 Security MisconfigurationUp from 5th to 2nd
A06 Vulnerable and Outdated ComponentsA03 Software Supply Chain FailuresWidened from known vulnerabilities to the whole supply chain
A02 Cryptographic FailuresA04 Cryptographic FailuresDown from 2nd to 4th
A03 InjectionA05 InjectionDown from 3rd to 5th
A04 Insecure DesignA06 Insecure DesignDown from 4th to 6th
A07 Identification and Authentication FailuresA07 Authentication FailuresShorter name
A08 Software and Data Integrity FailuresA08 Software or Data Integrity FailuresSame rank
A09 Security Logging and Monitoring FailuresA09 Security Logging and Alerting FailuresEmphasis on alerting and acting, not only recording
A10 Server-Side Request Forgery (SSRF)A10 Mishandling of Exceptional ConditionsNew 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

NameWhat it isMain use
OWASP Top 10The most critical web-app risks grouped into ten categoriesPrioritization, training, a shared vocabulary
OWASP ASVSA detailed verification standard of web-app security requirements (about 350 in 5.0, three levels)Writing requirements, scoping assessments and contracts
CWEMITRE's catalog of software weakness typesClassifying root causes; each Top 10 item groups several CWEs
CVEAn ID for a specific vulnerability in a specific productChecking 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:

How to check your own app

1

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.

2

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.

3

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.

4

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.

1

Start at the top (A01–A03) in your own app

Audit access control, configuration, and dependencies first; the most frequent incident sources cluster here.

2

Check config and dependencies (A02, A03) mechanically

Tighten production config (no debug exposure) and make dependency CVE monitoring a mechanism.

3

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.

Sources

FAQ

QWhat is the OWASP Top 10?
A

It's a list the non-profit OWASP (Open Worldwide Application Security Project) publishes every few years of the 'most critical web-application security risks,' organized into ten categories. It isn't a set of attack instructions; it's a common language developers and operators use to check 'where do I at least need to look.' The current edition is the 2025 version (announced November 2025); the previous one was 2021.

QWhat is number one on the OWASP Top 10?
A

As in 2021, the 2025 edition is led by Broken Access Control: the design flaw where being logged in is treated as being allowed, without checking whether that user may actually perform that action or touch that data. IDOR (reaching someone else's data by supplying their ID) and SSRF, which was merged in for 2025, both belong to this category.

QIf I cover the OWASP Top 10, am I safe?
A

No. The Top 10 is the ten most representative categories, not a checklist that guarantees sufficiency. Use it as a starting point for prioritization and gap-finding, and also cover the basics it doesn't directly address: dependency CVE monitoring, secret management, backups, and detection.

QWhat changed between the OWASP Top 10 2021 and 2025?
A

Two categories were added and one was merged. The new ones are Software Supply Chain Failures (A03, which widens 2021's Vulnerable and Outdated Components to cover the build and distribution path) and Mishandling of Exceptional Conditions (A10). SSRF is no longer its own category; it was merged into A01 Broken Access Control. In the ranking, Security Misconfiguration rose from 5th to 2nd, Cryptographic Failures fell from 2nd to 4th, and Injection from 3rd to 5th.

QHow is the OWASP Top 10 different from OWASP ASVS?
A

The Top 10 is an awareness list that narrows 'where it's dangerous' to ten items; it isn't a pass/fail standard. ASVS (Application Security Verification Standard), also from OWASP, is a verification standard: version 5.0, published May 2025, lists around 350 concrete requirements across three levels of assurance. For writing security requirements or defining the scope of an assessment or a contract, ASVS is the better fit.

QCan I use the OWASP Top 10 as a security testing standard?
A

Not as is. Each item is a broad grouping of dozens of CWEs (types of weakness), so it isn't written in a form you can mark as met or not met. OWASP itself describes the Top 10 as a starting point rather than a testing or audit standard. When scoping an assessment, a practical approach is to prioritize with the Top 10 and take the concrete checks from a standard such as ASVS.