Sample report · 29 October 2026 · Bardstar

Sample security report: Invoicer, a demo app

This is a full Bardstar review of a small invoicing app that we built and own, so we could publish everything. It is an example, not a client. Every finding below is real on that demo app, was proven with a real request, fixed, and tested again.

The result

9 problems: 5 Critical, 2 High, 1 Medium, 1 Low. All 9 fixed and retested. The worst let anyone on the internet read every customer’s invoices and uploaded ID documents, read every user’s email from an open admin endpoint, unlock the paid plan without paying, and use a master key that was sitting in the website’s own code.

IDSeverityWhat a stranger could doAfter
F-01CriticalRead and change every user’s invoices from any accountFixed
F-02CriticalUse a master key shipped in the website code to bypass every ruleFixed
F-03CriticalFake a payment to unlock the paid plan for freeFixed
F-05CriticalOpen any customer’s uploaded ID document with a guessable linkFixed
F-06CriticalRead every user’s email and the revenue total with no loginFixed
F-04HighSet their own price at checkoutFixed
F-07HighMake the AI assistant fetch another user’s invoicesFixed
F-08MediumGuess passwords without limit; reuse a reset link that never expiresFixed
F-09LowRead internal error details that help an attackerFixed

What the scanners missed

We also ran the standard free scanners. They flagged a few key-like strings and some build-tool advisories. They found none of the 9 problems above. Every one came from testing the running app with two accounts, a forged payment and an anonymous visitor. That is the gap a review closes.

What’s inside the full report

Honest limits: the demo runs locally with a small database that stands in for a hosted one, and its AI assistant uses a fixed stand-in model, so that finding is proven at the tool boundary. The report says so where it matters.