Prompt · Developer Tools

Security Audit

Hunts for OWASP-style vulnerabilities in code that handles auth, input, or data.

Have ready: Paste the code handling auth, input, or data access

Fill in · 3 fields

PASTE THE CODE, AUTH, INPUT HANDLING, QUERIES, FILE/SHELL ACCESS, CRYPTOLANGUAGE + FRAMEWORKWHO THE ATTACKER IS / WHAT IS AT STAKE, OR "GENERAL"

Your prompt

Security-review this code. Be adversarial: assume the attacker controls all input.

Code:
[PASTE THE CODE, AUTH, INPUT HANDLING, QUERIES, FILE/SHELL ACCESS, CRYPTO]
Language/framework: [LANGUAGE + FRAMEWORK]
Threat model notes: [WHO THE ATTACKER IS / WHAT IS AT STAKE, OR "GENERAL"]

Check for: injection (SQL, command, template, LDAP), auth bypass, IDOR, broken access control, XSS, CSRF, SSRF, path traversal, insecure deserialization, weak crypto, secrets in code, mass assignment, race conditions in auth flows.

For each finding: severity (Critical/High/Medium/Low), the exact vulnerable lines, how an attacker exploits it (concrete, not theoretical), and the fix with corrected code.

Then list what you checked and found clean, so I know the review had coverage. Do not pad with generic advice.

Paste it into Muse or any assistant. Blank fields stay as [brackets].

More like this

Merge Conflict Resolver

Coverage Gap Finder