Bologu and the OWASP Top 10:2025
The OWASP Top 10 is the most widely referenced list of web application risks; the latest edition is 2025. Every finding in a Bologu report is labelled with its category (for example OWASP A01:2025). This page sums up what each category means, what Bologu checks for it, and what automated tools can't check.
OWASP itself says the Top 10 is an awareness document, not a checklist or a compliance standard. A Bologu scan doesn't mean a site "passes OWASP"; it shows whether your site has the risks most often found in each category.
A01:2025 Broken Access Control
Users can reach or change data that isn't theirs, including making the server open internal addresses (SSRF), which joined this category in 2025.
Bologu checks
- Supabase / Firebase tables readable without login (the Deep scan actually tries)
- RLS policies that allow every row, only check login, or trust user_metadata
- APIs using service_role without filtering by owner, and admin checks done only in the page
- SSRF, path traversal, open redirects and personal data embedded in pages
Still needs a person: Logging in as several real accounts and trying to reach each other's data
A02:2025 Security Misconfiguration
Insecure settings, such as debug mode left on, secret files exposed or missing security headers.
Bologu checks
- Security headers (CSP, HSTS, clickjacking), CORS and cookies
- Reachable .env files, .git folders, source maps and directory listings
- Debug mode, public API docs pages, and email SPF/DMARC
Still needs a person: Server and cloud settings that can't be seen from outside
A03:2025 Software Supply Chain Failures
Risk from the packages and outside services your site depends on, both vulnerable versions and packages carrying malware.
Bologu checks
- Locked versions and libraries your pages load, compared with OSV.dev at scan time
- Vulnerabilities exploited in the wild (CISA KEV) and package versions that are malware
- Lockfiles, npm ci builds, * or latest versions, and packages that don't exist
Still needs a person: Reviewing the build pipeline and the permissions of CI tokens
A04:2025 Cryptographic Failures
Wrong or missing encryption, or secrets stored in a way that's easy to recover.
Bologu checks
- HTTPS, HSTS, old TLS versions and certificates about to expire
- Passwords stored without hashing or hashed with MD5/SHA
- Guessable random tokens and disabled certificate checks
Still needs a person: Encryption key management and encryption of data in the database
A05:2025 Injection
User input ends up executed as a command, such as SQL injection or XSS.
Bologu checks
- SQL built from strings, shell commands built from variables, and user values inserted as HTML (in code)
- Supabase filters built from text users type
- Data saved without validating its shape
Still needs a person: Sending test payloads to the live site (Bologu only reads, so it doesn't)
A06:2025 Insecure Design
Systems designed without thinking about cheating or overuse.
Bologu checks
- Prices taken from the browser and webhooks that grant things twice
- AI endpoints without call or length limits and without a daily cap
- Forms without spam protection, unchecked uploads and APIs without row limits
Still needs a person: Business logic such as coupons, credits and steps that can be skipped
A07:2025 Authentication Failures
Weak login and identity checks, including keys and passwords written into code.
Bologu checks
- API keys and passwords leaked in pages or code
- Supabase Auth settings: email confirmation, password length, CAPTCHA, rate limits and Redirect URLs
- JWTs read without verifying the signature, unlimited login attempts and leftover test accounts
Still needs a person: Password reset, OTP and session flows in custom-built login systems
A08:2025 Software or Data Integrity Failures
Trusting data or code without checking that it really comes from the right source.
Bologu checks
- Stripe, Clerk and GitHub webhooks that don't verify signatures
- CDN scripts without integrity (SRI)
Still needs a person: Deployment and automatic update processes
A09:2025 Security Logging & Alerting Failures
No logs or alerts, so attacks go unnoticed, or logs that store secrets.
Bologu checks
- No error alerting such as Sentry (a tip, it doesn't lower the grade)
- Server logs and browser console output that print tokens or passwords
Still needs a person: Checking that real attacks are recorded and someone sees them
A10:2025 Mishandling of Exceptional Conditions
Poor error handling, such as revealing internal details or letting requests through when a permission check breaks.
Bologu checks
- Error pages that show stack traces, SQL or file paths
- Permission checks that let requests through when they error (fail open)
- Calls to outside services without a timeout
Still needs a person: Testing how the system really copes with malformed input and outages
Start with a free scan
Scan your website for free with no sign-up, then connect GitHub or Supabase for a deeper check. If you want a person to actually try to break in, request a pen test quote.
