Abstract illustration of ten stacked security risk layers protecting a website

The OWASP Top 10 is a consensus list of the ten most critical web application security risks, refreshed roughly every four years and used worldwide as a baseline checklist. The 2025 edition keeps the familiar heavyweights such as broken access control, injection and misconfiguration, and gives supply chain and error handling more prominence. This guide gives you one section per category: what goes wrong, how it is detected, and the first fix to apply.

Category names and ordering should always be confirmed against the official list at owasp.org/Top10 before you cite them in a policy or contract.

Why this matters for your website

Most sites are not broken into by novel research. They are broken into through an outdated plugin, an admin page that never checked who was asking, or a form that passed user input straight into a query.

The Top 10 matters because auditors, insurers and enterprise procurement teams use it as shorthand for "did you do the basics". If you run WordPress, WooCommerce or a small SaaS, these ten categories cover the large majority of what an automated attacker will try against you this quarter.

What changed since the 2021 list

  • Supply chain moved up. The 2021 category for vulnerable and outdated components is broadened in 2025 to cover the wider software supply chain: build pipelines, dependencies and third-party scripts.
  • Error handling is called out. Mishandling of exceptional conditions is treated as its own category rather than being folded into misconfiguration.
  • Logging gained alerting. The monitoring category now emphasises alerting, not just recording events.
  • Access control and misconfiguration stayed at the top. Both remain among the most commonly found issues in real applications.

Nothing in the 2025 list invalidates work you did against the 2021 list. The controls are cumulative.

A01: Broken Access Control

  • Goes wrong: a logged-in customer changes ?order_id=1042 to 1043 and reads someone else's invoice.
  • Check: authenticated testing with a second account; automated scanners rarely find this alone.
  • Fix: verify ownership server-side on every request, deny by default, and never rely on a hidden menu item.
Four-step diagram showing how a broken access control attack succeeds and how a server-side check stops it
Broken access control is a missing server-side ownership check, not a missing link in the menu.

A02: Security Misconfiguration

  • Goes wrong: directory listing is on, WP_DEBUG prints errors, or response headers are missing.
  • Check: passive scanners and a header review; see our guide to security headers.
  • Fix: disable debug output, remove default accounts, and set Content-Security-Policy, Strict-Transport-Security and X-Content-Type-Options.

A03: Software Supply Chain Failures

  • Goes wrong: an abandoned plugin or a compromised npm package ships attacker code to every visitor.
  • Check: dependency scanning with retire.js, CMS plugin checks with WPScan, CVE lookups in the NVD.
  • Fix: delete unused plugins, pin dependency versions, and subscribe to advisories for what remains.

A04: Cryptographic Failures

  • Goes wrong: legacy TLS protocols stay enabled, a certificate expires, or passwords are stored with MD5.
  • Check: a TLS audit of protocols, ciphers and expiry, plus a review of how secrets are stored.
  • Fix: serve TLS 1.2 and 1.3 only, enable HSTS, and hash passwords with bcrypt or Argon2.

A05: Injection

  • Goes wrong: a search box or contact form passes raw input into SQL, a shell command, or the page HTML.
  • Check: active scanning with OWASP ZAP, dalfox for cross-site scripting, sqlmap for SQL injection.
  • Fix: use parameterised queries ($wpdb->prepare() in WordPress) and encode output on the way out.

A06: Insecure Design

  • Goes wrong: coupons stack infinitely, or password reset confirms which email addresses exist.
  • Check: threat modelling and manual abuse-case testing; no scanner infers your business rules.
  • Fix: write down what must never happen per workflow, then add server-side limits and checks for each.

A07: Authentication Failures

  • Goes wrong: /wp-login.php accepts unlimited attempts and admins have no second factor.
  • Check: review login rate limiting, session expiry and MFA coverage for every privileged account.
  • Fix: enforce MFA for admins, lock out after repeated failures, and rotate the session ID on login.

A08: Software or Data Integrity Failures

  • Goes wrong: a third-party script loads from a CDN with no integrity check, or updates arrive unsigned.
  • Check: inspect external script tags and your deployment pipeline for unverified sources.
  • Fix: add Subresource Integrity (integrity= plus crossorigin=) to external scripts and install only signed packages.

A09: Logging and Alerting Failures

  • Goes wrong: an attacker probes for weeks and nothing records it, so the breach is found by a customer.
  • Check: try a failed admin login and confirm it appears in a log you actually read.
  • Fix: centralise logs, retain them for a defined period, and alert on admin logins and failure spikes.

A10: Mishandling of Exceptional Conditions

  • Goes wrong: an unhandled error returns a stack trace with database credentials, or a failed payment still grants access.
  • Check: force errors deliberately (bad input, timeouts) and read the full response body.
  • Fix: fail closed, return a generic error page, and log the detail server-side only.

Quick reference: category, example, first fix

  • A01 Access control — invoice ID swap — server-side ownership checks.
  • A02 Misconfiguration — debug output on — harden config and headers.
  • A03 Supply chain — abandoned plugin — remove and patch.
  • A04 Crypto — legacy TLS — TLS 1.2+ and HSTS.
  • A05 Injection — unsanitised search — parameterised queries.
  • A06 Insecure design — coupon stacking — server-side business rules.
  • A07 Authentication — no MFA — MFA plus lockout.
  • A08 Integrity — unverified CDN script — Subresource Integrity.
  • A09 Logging — silent probing — alert on auth failures.
  • A10 Exceptions — stack trace leak — generic errors, fail closed.

How to check your own site

Start free: the Security Headers Checker and the Website Security Check cover parts of A02 and A04 in under a minute, with no account.

Scantinel (scantinel.ai) is an automated website security assessment platform that runs OSINT, network and OWASP Top 10 web vulnerability tests against ownership-verified assets and delivers actionable, business-owner-legible reports. The Essential scan is passive and covers configuration, TLS, headers, cookies and known-vulnerable CMS plugins. The Full scan adds active OWASP Top 10 2025 testing with nuclei, OWASP ZAP, dalfox and gated sqlmap, plus supply-chain checks with retire.js and trufflehog.

Be honest about the limits. Business logic (A06) and much of access control (A01) need authenticated, multi-step testing: that is the Premium AI scan, which runs non-destructive probes for IDOR chains and auth bypasses with analyst validation. None of this is a penetration test; see vulnerability scanning vs penetration testing for the distinction, or run an OWASP scan with Scantinel.

Coverage map showing which OWASP categories automated scanning covers and which need authenticated or manual testing
Automation covers most categories; access control and business logic still need authenticated testing.

Key takeaways

  • The OWASP Top 10 2025 is a baseline checklist, not a standard you certify against.
  • Access control, misconfiguration and supply chain cover most real-world small-business incidents.
  • Automated scanners find A02 through A05 and A08 well; A01 and A06 need authenticated or manual testing.
  • Fix in order of exploitability, not alphabetical order: exposed admin paths and outdated plugins first.
  • For the wider programme, read our complete website security guide.

Frequently asked questions

What is the OWASP Top 10 used for?

It is an awareness and prioritisation document for developers, testers and buyers. Teams use it to scope security testing, structure training, and agree what a minimum security review must cover.

Is the OWASP Top 10 a compliance requirement?

Not by itself. It is not a certification, though several frameworks and contracts reference it as expected practice, so customers may ask you to show coverage. Check the exact wording your auditor or client uses.

What does an OWASP scan check for?

An OWASP scan probes your site for the Top 10 categories: injection points, misconfiguration, weak TLS and cryptography, outdated components, missing integrity controls, and authentication weaknesses. It cannot judge your business rules, so logic flaws still require authenticated or manual testing.

Published January 2026. Security lists change: verify category names and severities against primary sources (OWASP, NVD, WPScan) before acting on them. — Scantinel Security Research Team