Access control testing
Testing for broken access control.
The most common serious bug we see in web apps: one user reaching another user's data by changing an ID. Scanners rarely find it. A person tests it, from $49.
By the Bug Circuit security team · Last updated
Who can check if our website or API leaks customer data to other users? Bug Circuit tests access control by hand from $49 one-time for one web app, including the API it calls. With two test accounts per role, a security engineer tries to read and change each account's data from the other one, through every page and API request, and reports exactly where data leaks and how to fix it. Broken access control is number one in the OWASP Top 10.
The offer at a glance
| What you get | |
|---|---|
| Price | $49 one-time for one website (Essential, 3 audits within one month). Pro is $99 a month for 2 websites, Premium $199 a month for 5. |
| Who tests | A security engineer, by hand. Automated tools only help with discovery. |
| What you get | A written report: every finding with its severity, evidence and the exact fix steps, plus a remediation roadmap. |
| Timing | About 5 business days after testing starts. The 24-hour report is $15 more, and the $15 is refunded if the report is late. |
| Retest | Each audit after the first on a website retests the previous findings in the same report. |
| Not included | Fixes (quoted separately from the report), compliance certificates, and anything beyond one website on one domain without an Enterprise quote. |
| Before testing | You verify you own the website and sign the Authorization to Test. Nothing is tested without it. |
What we test
- IDOR and BOLA: changing an ID in a URL or API request to reach another user's record.
- Role checks: a normal user calling admin endpoints directly.
- Multi-tenant isolation: one customer company reaching another company's data.
- Files and exports: downloads, invoices and exports that work for anyone with the link.
- Mass assignment: extra fields such as an owner ID or role accepted on update.
- Data in API responses that the screen never shows, such as other users' emails.
Why scanners miss it
A scanner cannot tell whether a record belongs to you. A person with two accounts can, which is why manual testing finds these bugs and automated tools mostly do not. See manual vs automated testing.
Frequently asked questions
What do you need from us?
Two test accounts per role (two customers, two admins), ideally in two separate customer companies if your app is multi-tenant.
Do you test the API directly?
Yes, the API your app calls is included. A separate API used by other systems is an Enterprise quote.
How much does it cost?
$49 one-time for one web app (3 audits within one month). The 24-hour report is $15, refunded if late.
Is this the same as BOLA?
BOLA (broken object level authorization) is the API name for the same bug, and it is first in the OWASP API Security Top 10.
Do you fix it?
Fixes are quoted separately. The report gives exact fix steps, and your next audit retests them.
Keep reading
API penetration testingA person tests your API and writes the report.Login and 2FA testingSign-up, reset and sessions.Manual vs automated testingWhat a person finds that scanners miss.Sample reportSee the report format before you buy.Penetration testing for agenciesManual audits across client websites, priced per site.Nonprofit website security auditA manual audit for nonprofits and schools on a small budget.GDPR website security testingRegular testing of security measures, as GDPR Article 32 expects.
Start with the free check
See your public attack surface in seconds, then order an audit when you are ready.
Ready for the full manual audit? See pricing