Skip to main content

Scenario

Your CI pipeline flagged a HIGH severity finding in a pull request. The developer who wrote the code is unfamiliar with the vulnerability class. You need to understand it, fix it, and ship it — fast.

Step 1: Find out what’s flagged

Step 2: Get the AI explanation

Step 3: Verify the finding

The confidence is 62% — this might be a false positive. Check the file:
It’s real — no requireAuth middleware. Confirm:

Step 4: Generate an AI fix

Option 2: Protect the entire router (more secure) If all routes in this file require authentication, protect the router:
Option 3: Add authorization check inside the handler If some routes in the file are public, add the check inside:
Recommended: Option 2 if all routes need auth, Option 1 otherwise. Also consider: Does the handler verify that userId matches the authenticated user? IDOR (Insecure Direct Object Reference) is common here — fetching billing for any userId when the caller can only see their own is also a vulnerability.
The PR description:

Step 6: Rescan to confirm

After merging:

Time invested

Without ZenVeil, this vulnerability might have shipped to production — where it would expose billing data for every user to anyone who knows the URL.