Skip to content
winfunc
winfunc Scanner

Detection, proof, and the fix, in one workspace.

SAST, SCA, IaC, secrets, and container scanning with validated findings, patches as pull requests, and analytics, all connected to the same application context.

Pricing
  1. acme
  2. /billing-api
  3. /Vulnerabilities
  4. /WF-1042
Critical
Sourceroutes/invoices.ts:18
req.params.invoiceId
Sourceroutes/pdf.ts:31
req.query.invoice
1
Passed to the service without the caller's tenantinvoices.get(id)services/invoices.ts:42
2
Repository looks the invoice up by id alonerepo.findInvoice(id)repo/invoices.ts:71
Sinkrepo/invoices.ts:77
db.query("SELECT * FROM invoices WHERE id = $1", [id])

Cross-tenant invoice read through an unscoped lookup

CriticalCVSS 9.1
Weakness
CWE-639 · Authorization bypass
Confidence
97
Validation
Exploitable
Proof
Tenant A read tenant B's invoice in the sandbox
Finding · source to sinkIllustrative data
  1. Every place attacker-controlled input enters.
  2. Each hop is recorded with the code that carried the value.
  3. The dangerous operation, with no check on the path.
  4. Reproduced in an isolated sandbox before it reached you.
Enterprise-ready

Ready for your security review.

Review access, retention, model providers, administrative events, and deployment responsibilities. Enterprise options and terms are scoped by agreement.

Identity and access

  • Repository-scoped access

    Authorize selected repositories and review user and administrator permissions before expanding scope.

  • Federated identity optionsEnterprise

    Confirm the identity provider, protocol, and configured deployment in the enterprise agreement.

  • User lifecycle reviewEnterprise

    Agree provisioning, deprovisioning, session invalidation, and access-review responsibilities.

  • Revocable MCP keys

    Read-only MCP keys are stored as SHA-256 digests and support revocation. Review other credential types separately.

Data protection

  • Retention by data category

    Working copies, caches, findings, resume state, operational records, backups, and provider data need an agreed lifecycle.

  • Model-provider terms

    Agree the provider/account, processing region, training-use restrictions, and retention before granting access.

  • Credential protection

    Onboarding test credentials support authenticated encryption when storage is configured. Confirm other storage and transport protections.

  • Event and trace boundaries

    API event metadata excludes bodies and credential headers; agent/session traces are separate retained artifacts to review.

Deployment and models

  • Customer-controlled hostingEnterprise

    Hosting and infrastructure, access, upgrade, and support responsibilities are scoped by agreement.

  • Isolated environmentsEnterprise

    Review the proposed network, storage, identity, model, and administrator boundaries.

  • Bring your own model credentialsEnterprise

    Confirm providers and account controls. Customer-owned keys alone do not establish private inference or zero retention.

  • Open-weight model evaluation

    Public research used open models. Confirm the proposed endpoints, infrastructure, and supported workflow for your deployment.

Oversight

  • Administrative event review

    Confirm event coverage, access, retention, filtering, saturation behavior, and export for the deployment.

  • Customer change approval

    Agree read and pull-request permissions separately. Keep patch review, verification, and release approval with your team.

  • Policy and scope controls

    Agree review policies, permitted actions, test environments, exceptions, and reporting for the purchased workflow.

  • Named supportEnterprise

    Support, escalation, response targets, and incident-notice terms are confirmed in the contract.

Start with one repository

Bring us your hardest codebase.
We'll bring the proof.

Scope a first audit with our security engineers. You get findings with traces, reproduction evidence, and patches ready for review.

Scoped with you. Delivered with evidence.