Senior pentesters · written reports

Real pentesters.Real findings.

A small team of senior security engineers who hand-test your applications and write the report ourselves. Not a scanner SaaS — a partner you can call when something breaks.

  • Every finding hand-validated by a named pentester
  • Written report, walkthrough call, retest included
  • OSCP, OSWE, GXPN — credentials your auditors recognize
acme-q2-report.pdf
finding 01 / 16
Critical · 9.80-clickCWE-640

Account takeover via password-reset email injection

Summary

The reset endpoint accepts email as an array and dispatches the same token to every address — attacker submits the victim's email alongside their own and receives a valid reset link.

Proof of concept
POST /api/auth/password-reset { "email": [ "ceo@acme.com", // victim "attacker@evil.io" ] } ↳ reset link delivered to both inboxes
Impact

Pre-auth, 0-click takeover of any account — admins included.

Fix · verified

Coerce email to string; bind token to one recipient.

Inside every verified finding

From vague bugs to fix-ready findings.

Most reports stop at the vulnerability name. Ours show exactly what broke, why it matters, how to reproduce it, and what your team should change.

Typical report
FINDING-014
High

Broken Access Control

Severity

High

Recommendation

Improve authorization.

Evidence

Engineer needs another meeting to understand what to fix.
BugSwagger finding
BS-2026-0142
Critical · 8.6

IDOR — cross-tenant invoice access

/api/invoices/:id · CWE-639

Impact

Tenant B's invoices accessible to any Tenant A user. Cross-tenant PII & billing exposure.

Evidence
GET /api/invoices/9281 ↳ 200 OK · returned tenant B invoice
Recommended fix

Enforce tenant-scoped queries at the data layer: WHERE tenant_id = current_tenant().

Reproduced · re-tested clean

Every verified finding ships as a self-contained brief — severity, evidence, impact, fix, and retest status — so your engineers can ship the patch without another clarification call.

How an engagement runs

Five conversations, not a dashboard

Every engagement is delivered the same way — by a named pentester, with you on every step.

  1. BS
    ScopePentesterDay 0
    Quick call to agree on scope, timeline, and rules of engagement.
  2. YOU
    AccessYour teamDay 1
    You share staging access, test accounts, and architectural context.
  3. BS
    TestingPentesterDay 2–9
    Hands-on testing begins. Daily updates if anything urgent surfaces.
  4. BS
    ReviewPentesterDay 10–11
    You receive the report and we walk through every finding live.
  5. BS
    FixPentesterDay 30–60
    You ship the fixes; we re-verify and update the report for your auditors.
Client stories

What teams say after working with us

2020
“BugSwagger performed a full pentest of our online video editing platform at WeVideo, Inc. The team's thorough examination found vulnerabilities that other researchers had missed. Every item was disclosed in a very clear and detailed report that made it extremely easy for our team to understand the nature of and to resolve the vulnerabilities. The team was also very responsive and responsible in notifying us of severe findings in an immediate manner. We can easily recommend their services for anyone interested in great pentesting.”
Found critical vulnerabilities others missed
Jonathan Huang
Jonathan Huang
Cyber & Data Privacy Lead · WeVideo
WeVideo
2021
“The outputs generated by the BugSwagger Team were great, they detailed the bugs found with a very detailed presentation to us. This helped us out on fixing the vulnerabilities in an assertive manner. Great work by them!”
Detailed vulnerability reports
Filipe de Alcântara
Filipe de Alcântara
CTO · GeekHunter
GeekHunter
24h
First findings shared
0
False-positive handoff
100%
Findings hand-verified
Trusted by teams shipping critical software
WeVideo
Shoplo
Audiosocket
Eskimi
CompanyCam
GeekHunter
CubiCasa
SOUNDREEF
WeVideo
Shoplo
Audiosocket
Eskimi
CompanyCam
GeekHunter
CubiCasa
SOUNDREEF
FAQ

Frequently asked questions

Can’t find the answer you’re looking for? Reach out to us.

11 more questions on pricing, scope, methodology, retesting, compliance and more.
Browse all FAQs
Start an engagement

Get your first verified finding.

Tell us what you are protecting. We will respond within one business day with a scoped proposal — written by a pentester, not a sales rep.

Security insights, in your inbox

Occasional notes on what we are seeing in real engagements — auth bugs, cloud incidents, and patterns worth knowing. No spam.

We care about your data. Read our privacy policy.