Web applications have always faced serious security issues, but with today’s digitalization movement and add in artificial intelligence tools and defenders are constantly looking over their shoulders in an effort to seek any kind of assistance.

To that end, the Open Worldwide Application Security Project (OWASP) released the eighth version of its Top Ten list of web application security risks, maintained since 2003.

In keeping with the dynamic nature of cybersecurity, the new list added new categories like Software Supply Chain Failures and Mishandling of Exceptional Conditions for 2025. The new list also consolidates Server-Side Request Forgery into the category of Broken Access Control, which remains in the number one position as the most serious application security risk.

The OWASP Top Ten list includes:

Broken Access Control

1. This maintains its position top position from the last list as the most serious application security risk; the contributed data indicates on average, 3.73 percent of applications tested had one or more of the 40 Common Weakness Enumerations (CWEs) in this category. As indicated by the dashed line in the above figure, Server-Side Request Forgery (SSRF) has been rolled into this category.

Schneider Bold
Security Misconfiguration

2. This category moved up from 5 in 2021 to 2 in 2025. Misconfigurations are more prevalent in the data for this cycle. Three percent of the applications tested had one or more of the 16 CWEs in this category. This is not surprising, as software engineering is continuing to increase the amount of an application’s behavior based on configurations.

Software Supply Chain Failures

3. This is an expansion of the 2021 list’s Vulnerable and Outdated Components to include a broader scope of compromises occurring within or across the entire ecosystem of software dependencies, build systems, and distribution infrastructure. This category was overwhelmingly voted a top concern in the community survey. Additionally, this category has 5 CWEs and a limited presence in the collected data. However, we believe this is due to challenges in testing and hope that testing catches up in this area. This category has the fewest occurrences in the data, but also the highest average exploit and impact scores from CVEs.

Cryptographic Failures

4. This falls two spots from 2 to 4 in the ranking. The contributed data indicates, on average, 3.80 percent of applications have one or more of the 32 CWEs in this category. This category often leads to sensitive data exposure or system compromise.

Injection

5. This falls two spots from 3 to 5 in the ranking, maintaining its position relative to Cryptographic Failures and Insecure Design. Injection is one of the most tested categories, with the greatest number of CVEs associated with the 38 CWEs in this category. Injection includes issues from Cross-site Scripting (high frequency/low impact) to SQL Injection (low frequency/high impact) vulnerabilities.

Insecure Design

6. This slides two spots from 4 to 6 in the ranking. This category ended up introduced in 2021. There has been noticeable improvements in the industry related to threat modeling and a greater emphasis on secure design.

Authentication Failures

7. This maintains its position at 7 with a slight name change (prevously it was Identification and Authentication Failures) to more accurately reflect the 36 CWEs in this category. This category remains important, but the increased use of standardized frameworks for authentication appears to be having beneficial effects on the occurrences of authentication failures.

Software or Data Integrity Failures

8. This category continues at 8 in the list. This category focuses on the failure to maintain trust boundaries and verify the integrity of software, code, and data artifacts at a lower level than Software Supply Chain Failures.

Logging & Alerting Failures

9. This retains its position at 9. This category has a slight name change (previously Security Logging and Monitoring Failures) to emphasize the importance of the alerting functionality needed to induce appropriate action on relevant logging events. Great logging with no alerting is of minimal value in identifying security incidents. This category will always be underrepresented in the data, and was again voted into a position in the list from the community survey participants.

Mishandling of Exceptional Conditions

10. This is a new category for 2025. This category contains 24 CWEs focusing on improper error handling, logical errors, failing open, and other related scenarios stemming from abnormal conditions that systems may encounter.

Click here for more on the OWASP Top Ten.

Pin It on Pinterest

Share This