Pular para o conteúdo

// Security by tool

Security for apps built with Base44

6 minUpdated July 25, 2026By Ler em português

Quick answer

In July 2025 Wiz found a critical flaw in Base44 (Wix’s vibe coding platform): two API endpoints, register and OTP verification, did not require authentication. Since the app_id was public in the app URL and manifest.json, an attacker created a verified account using only that app_id and entered private applications that were supposed to be SSO-restricted. Several of those apps stored PII and ran HR operations.

Wix fixed it within 24 hours and found no sign of exploitation. But the case is a portrait of the vibe coding risk: the platform accelerates, and access control (who can register, who can enter) stays fragile by default. If you shipped on Base44 and have a private app or sensitive data, review how registration and authorization actually work.

What to review in a Base44 app

The specific flaw was fixed in the platform, but the risk pattern (a public identifier becoming an access key, an endpoint with no auth) is what you need to check in YOUR app.

Risk patterns in Base44 apps
PatternWhy it mattersImpact
Public identifier as a keyapp_id/ids exposed in URL and manifestImproper access if they become credentials
Endpoint with no authenticationOpen register/OTP were the vectorAccount created in a private app
SSO that does not cover every doorRestriction at login, not each endpointBypass via an alternate path
Sensitive data in a "private" appPII/HR trusting only obscurityLeak if access falls

How RET reviews a Base44 app

RET tests what a user with no invite can do: can I register in a private app? Does an endpoint respond with no auth? Does a public id (app_id, user_id) become access to data it should not? It checks whether SSO covers every door, not just the login screen. Each finding ships with reproduction steps.

For the first pass, the Promptbook guides checking registration, authorization and exposed ids. When there is PII or a B2B sale, Risk Review reads the access flows and says what to close first.

  • Test registration and access with no invite in a private app.
  • Endpoints checked one by one: none returns data without auth.
  • SSO covering every door, not just the login.

You may already be exposed if

Signals that call for a review of a Base44 app.

  • Your app is "private" but you never tested whether you can register with no invite.
  • The access restriction is at login, not on each data endpoint.
  • You store PII or HR data trusting that the app is obscure.
  • A customer asked for proof that access is really restricted.

Want to know whether this happens in your system?

Manual pentest for web applications, APIs and apps, from R$9,500, with the Sprint run within 7 business days. We refund 50% if we find no flaw.

See price and timeline for my case

Frequently asked questions

Does the Base44 flaw still affect me?

The specific vulnerability Wiz found was fixed by Wix within 24 hours, with no sign of exploitation. But the pattern (a public id, an endpoint with no auth, SSO that does not cover every door) is what you should check in your own app, because access configuration is the publisher’s responsibility.

Is a private Base44 app really private?

It depends on how access is configured. The Wiz case showed apps "private by SSO" accessible via register/OTP endpoints with no auth. Real privacy comes from checking authorization on every door, not from hiding the URL.

How do I test my app’s access?

By trying what you should not: registering with no invite, calling an endpoint with no token, using a public id to reach data. It is the first test RET runs, and the Promptbook guides you to do it yourself.

Who runs the review at RET?

Gabriel Lima Ferreira, founder and lead pentester, with an authorized scope and reproducible evidence.

Keep reading