Skip to content
StratQuad

OWASP Top 10

2 min read

The Open Worldwide Application Security Project's awareness list of the most critical web application security risks, now in its 2025 edition.

At a glance

Owner
OWASP Foundation
Version
OWASP Top 10:2025
Applies to
Anyone building, buying or testing web applications and APIs
Mandatory
Voluntary; frequently referenced in contracts, procurement and testing scopes
Assessed by
Not an assessment standard; use OWASP ASVS for verifiable requirements
Cost model
Free

Key points

  • The Top 10 is an awareness document, not a standard. It names categories of risk, each mapped to many CWE weaknesses.
  • The 2025 edition, the eighth, is the first major update since 2021. It adds Software Supply Chain Failures and Mishandling of Exceptional Conditions.
  • Broken Access Control remains first and now explicitly includes server side request forgery.
  • For requirements you can test against, use the OWASP Application Security Verification Standard (ASVS).

The 2025 list

IDCategoryChange from 2021
A01:2025Broken Access ControlStill first; now includes server side request forgery (SSRF)
A02:2025Security MisconfigurationUp from fifth
A03:2025Software Supply Chain FailuresNew; broadens 2021's Vulnerable and Outdated Components
A04:2025Cryptographic FailuresDown from second
A05:2025InjectionDown from third
A06:2025Insecure DesignDown from fourth
A07:2025Authentication FailuresUnchanged position; renamed from Identification and Authentication Failures
A08:2025Software or Data Integrity FailuresUnchanged position
A09:2025Security Logging and Alerting FailuresRenamed from Security Logging and Monitoring Failures
A10:2025Mishandling of Exceptional ConditionsNew

How the list is built

OWASP combines contributed testing data, mapped to CWE weaknesses, with a community survey that allows emerging risks to be included before they show up in data. In 2025, eight categories came from the data and two, A03 and A09, from the survey. Each category groups related CWEs and is ranked using measures such as incidence rate, exploitability and impact.

Using it well

Practitioner note

Use the Top 10 to set a minimum in contracts and to train developers, but do not let "OWASP Top 10 tested" stand in for a test specification. A penetration test scope should name the ASVS level and the application's own business logic risks; access control flaws, which top the list, are almost always specific to how the application handles its own users and objects and are missed by automated scanning.

Common mistakes

  • Treating the Top 10 as a complete checklist and declaring an application "compliant".
  • Relying on automated scanners for A01 Broken Access Control and A06 Insecure Design, which they detect poorly.
  • Ignoring A03 because third party components are "the supplier's problem".
  • Logging security events but never alerting on them, which the 2025 rename to "Alerting Failures" is designed to highlight.

Sources

Suggest a correction