AI-Built App Security Checkup — Sample Audit Report

Prepared by: CapAIGC Security Review Subject: "TaskFlow" — demo SaaS application (Next.js 13 + Supabase) Report type: Static source-code security audit (sample report) Date: 2026-11-12 Scope: 8 source files, ~94 lines — client setup, auth library, 3 API routes, 1 component, database schema, dependency manifest

Sample report notice. This report was produced on a deliberately vulnerable demo codebase written for evaluation purposes. It is not a real client engagement. It demonstrates the exact format, evidence standard, and depth of a paid checkup: every finding below cites a real file and line, was independently re-verified by a human reviewer before inclusion, and ships with a fix prompt you can paste into your AI coding tool.


Executive summary

Overall risk: Critical. Security score: 17 / 100.

The application ships a full-access database key to every visitor's browser, has Row Level Security switched off on the table that stores user emails, and performs no authentication on endpoints that read profiles and accept file uploads. An unauthenticated attacker can read user PII and write files to the web root with no credentials at all. Do not deploy this code.

Severity Count
Critical 3
High 5
Medium 1
Low 0

Fix first (in this order): C1 → C2 → C3 → H1. These four close the unauthenticated data breach and file-write paths.


Findings

C1 — Supabase service-role key exposed in the browser bundle

C2 — Row Level Security disabled on profiles

C3 — Unauthenticated file upload with path traversal

H1 — Unauthenticated IDOR in the profile API

H2 — JWT fallback secret, tokens that never expire

H3 — Admin authorization via a client-controlled header

H4 — Stored XSS via unsanitized comment HTML

H5 — Public storage bucket for user documents

M1 — Outdated dependencies, including a known-vulnerable lodash


Scope, method, and limits

Method: Full manual read of every in-scope file (cross-file data-flow review), followed by independent re-verification of each finding's file/line evidence by a second reviewer. AI-assisted analysis with human review of every reported item.

Not covered by a static checkup: runtime/dynamic testing of the deployed app, dependency installation and npm audit execution, Supabase project settings beyond the provided schema, environment variables and deployed secrets, middleware and code not provided, infrastructure and DNS/TLS configuration. Items that depend on runtime behaviour are labelled "requires manual confirmation" rather than reported as confirmed.

What a clean report means: no confirmed findings in the reviewed scope — never a guarantee that an application is "secure".


CapAIGC Security Review — AI-assisted, human-verified code security checkups for AI-built apps. Sample report v1, 2026-11-12.