What is the OWASP Top 10?
The OWASP Top 10 is a widely used list of the ten most critical security risks for web applications, published by the Open Worldwide Application Security Project. It is an awareness document that groups common flaws, such as broken access control and injection, to help teams decide what to fix first.
How it works
The list is updated every few years from real vulnerability data and community input. It names risk categories, not individual bugs. The current edition ranks Broken Access Control first, followed by Security Misconfiguration, Software Supply Chain Failures, Cryptographic Failures, Injection, Insecure Design, Authentication Failures, Software or Data Integrity Failures, Security Logging and Alerting Failures, and Mishandling of Exceptional Conditions. Server-side request forgery, once separate, is now treated within access control. Check the OWASP site for the exact current wording.
A01 Broken Access Control (IDOR, missing role checks, RLS gaps)
A02 Security Misconfiguration (headers, debug mode, open storage)
A03 Software Supply Chain Failures (vulnerable libraries)
A04 Cryptographic Failures (weak TLS, leaked secrets)
A05 Injection (SQL injection, XSS)How to tell if your site is affected
- Any site with logins and user data should check access control first: can user A reach user B's records?
- Any site can have security misconfiguration: missing security headers, debug pages, public .env files or open cloud storage.
- If you use npm, Composer or WordPress plugins, outdated components make you subject to supply chain and known-vulnerability risks.
- If you build SQL, HTML or shell commands from input, the injection category applies to you.
How to fix it
Use the list as a checklist, not a scorecard. Start with access control and misconfiguration, which cause most real incidents.
Add ownership checks to every data endpoint, and enforce them in the database where you can (Supabase RLS, Firebase rules).
Set security headers, remove debug output and keep secrets in server-only environment variables.
Keep dependencies updated and monitor them for published vulnerabilities.
Log sign-ins and failures, and run an automated scan before each release, followed by a manual review for critical systems.
How ScanAnt checks for it
ScanAnt does not certify OWASP compliance. Its checks map onto several categories: the free quick scan covers headers, cookies, leaked keys and vulnerable libraries; the verified scan checks exposed files, certificates and open database access on Supabase or Firebase; the deep scan adds injection and redirect probes and known CVEs; the code scan reviews uploaded source for missing owner checks. Design flaws and business logic need human review.
Questions
Is the OWASP Top 10 a compliance standard?
No. It is an awareness list. Standards such as PCI DSS refer to it, and OWASP's ASVS is the detailed verification standard.
How often is it updated?
Every few years. Check owasp.org for the current edition, because rankings and names change between versions.
Does passing a scan mean I meet the Top 10?
No. A scan checks what it can observe. Passing it means no known problems were found there, not that every category is covered.
Where should a small team start?
Broken access control and security misconfiguration. Both are common, high impact and cheap to check.
Related terms
XSS
Untrusted text runs as script in your visitors' browsers.
Read →SQL injection
User input rewrites your database query.
Read →IDOR
Changing an ID in a request exposes another user's data.
Read →SSRF
An attacker makes your server fetch an address they pick.
Read →Check your own site
A free first look at any site: HTTPS, headers, cookies and leaked keys.
Open the matching check →
See if your site is affected
Free for any public site, no signup. Need the verified or deep scan? Choose the level on the scan page.
Choose a scan level →