Can this be tested from the outside?

Partly. MLVibeScan checks Firebase rules in the ZIP and controlled runtime signals; source and deep checks require purchase, domain verification and explicit consent.

Is blocking access in the UI enough?

No. Security decisions must be enforced server-side for every request, regardless of the client an attacker uses.

When is the finding fixed?

Only when the control holds in a controlled re-test and no contradictory source/runtime observation remains.

Security guidance for vibe apps

Firebase rules: why “if true” makes data public

Firebase browser configuration is normally public; Firestore and Realtime Database rules are the actual security boundary. An unconditional read or write rule exposes data even when sign-in appears to work.

Reviewed by René Matis · MATIS LABS · Updated 15 August 2026

The scan is free and takes about twenty seconds. You see straight away how many findings there are and how serious they are.

Scan your own app for free

How to recognise the problem

Critical patterns include `allow read, write: if true`, global wildcards and rules that only require any signed-in user without checking document ownership.

A working happy path does not prove this boundary. Always test with a second user, while signed out or with an intentionally forbidden input.

How to fix it reliably

Bind access to `request.auth.uid`, verify owner and role per path, and negative-test reads and writes with two accounts.

The control belongs at the server-side trust boundary. A hidden button, different client copy or browser-only validation is not a security control.

Re-test instead of hoping

MLVibeScan checks Firebase rules in the ZIP and controlled runtime signals. A re-test compares the stable protection target with the previous result and reports fixed, partially fixed, unchanged or regression.

Automated checks cover recurring patterns. High-risk business logic may additionally require an individually scoped penetration test.

What we check automatically

Firebase rules in the ZIP and controlled runtime signals
Confidence and counter-checking
Stable fingerprints for re-tests

Frequently asked questions

Can this be tested from the outside?: Partly. MLVibeScan checks Firebase rules in the ZIP and controlled runtime signals; source and deep checks require purchase, domain verification and explicit consent.
Is blocking access in the UI enough?: No. Security decisions must be enforced server-side for every request, regardless of the client an attacker uses.
When is the finding fixed?: Only when the control holds in a controlled re-test and no contradictory source/runtime observation remains.