7IT Solutions
7IT GuardHow it worksWhat it checksProofPlansLaunch ReviewFix guidesHelp

Is my Base44 app secure?

Base44 gives an app its hosting, its data tables and its sign-in in one place. Who may read, create, change or delete each record is a rule you set per table, and it is the part to check before launch.

What Base44 handles.

Hosting, user sign-in and a built-in database
Permission rules per data table, at record level and field level
A security scan in the dashboard covering seven issue types, from data permissions to exposed secrets and security headers
One-click fixes from the scan, with a checkpoint before each change

From the platform’s own documentation: Base44 docs: Running a security scan · Base44 docs: Managing data permissions

What stays yours.

The permission rule on every table: who can create, read, update and delete
Which tables are open to people who have not signed in
Backend functions that check who is calling before returning data
Keys for paid services kept out of what visitors can load
Whether the app itself is public or requires sign-in

Documented.

Public reports that involve Base44 or apps built on it, dated and linked. Each line says what its source says, and nothing more.

July 29, 2025An authentication bypass on private Base44 apps

Wiz Research found that the public app_id alone let anyone register a verified account on a private Base44 app through two undocumented endpoints. Reported on 2025-07-09, fixed by Wix within 24 hours, with no evidence of exploitation; disclosed 2025-07-29.

Source: Wiz Research, July 29, 2025
May 7, 2026About 380,000 public assets built with AI coding tools

eWeek reports that Red Access found about 380,000 publicly accessible assets created with AI coding tools, on platforms including Lovable, Replit, Netlify and Base44, and that around 5,000 of them exposed potentially sensitive information such as medical and financial records.

Source: eWeek, May 7, 2026

A five minute check.

In your own Base44 dashboard, in this order.

Run the security scanIn the app editor, open Dashboard, then Security, then Run Security Scan. Read data permission findings first.
Open each table’s permissionsSelect a data table and click Permissions. Read the rule for Read, Update and Delete, not only Create.
Look for All Users on private dataAll Users means anyone, even without signing in. Orders, messages and profiles should be Creator Only or matched to a user field.
Check backend functionsAny function that returns data should confirm who is asking. The scan flags functions that answer without a signed-in user.
Confirm who can open the appIn the app’s access settings, check whether it is public or limited to invited people, and that this matches the data inside.

Questions.

Was the 2025 Base44 issue fixed?

Yes. Wiz Research reported it on 2025-07-09; Wix fixed it within 24 hours and found no evidence of exploitation. It was a platform issue, separate from the permission rules each app owner sets.

What does Creator Only actually mean?

Per Base44’s docs, a person can only access the records they created. It suits personal data such as orders or submissions. Shared records need a field-based rule instead.

Can the scan fix everything for me?

It fixes what it can recognize. It cannot know that a table holding customer notes should never be visible to other customers unless the rule says so. Reading the rules against the business is the human part.

Check the public side now.

Ten seconds. We read only what any visitor’s browser already sees, and store nothing.

Opens the app security check on this site with your address filled in.

7IT Guard on GitHub

Check it on every push.

Add the 7IT Guard check to your repository. After every deploy it checks the live app from outside, preview and production, and keeps one comment on the pull request up to date. Nothing from your code is read or sent.

Add it to your repository.

Pick where your app deploys:

# .github/workflows/7it-guard.yml
name: 7IT Guard
on: deployment_status
permissions:
  id-token: write
  contents: write
  pull-requests: write
jobs:
  guard:
    if: github.event.deployment_status.state == 'success'
    runs-on: ubuntu-latest
    steps:
      - uses: XLSV777/7it-guard-check@v1
        with:
          site: https://yourapp.com

Save it as .github/workflows/7it-guard.yml with your own address. It never fails a build unless you set on-problem: block. Inputs and examples

Ask your AI builder.

Connect 7IT Guard once inside your builder, then ask in the chat:

Using 7IT Guard, check that my app is safe before I publish. Show me the 7IT Guard result as it is. My app: myapp.com

Each guide shows where to add the connector and how to read the 7IT Guard answer.

Launch Review

Your AI built it. Nobody checked it. I will.

A senior engineer goes through your live app and tells you what is leaking, what is broken and what to fix first, with the exact prompt that fixes it. Written report in 48 hours.

  • Fixed price
  • Database rules, keys, payments, email
  • Money back if nothing needs fixing
See the Launch Review

How it works, in four steps.

ScanCheck the protections any visitor’s browser can see, then run the deeper scan on an app you prove is yours.Ten seconds, on this siteRun the scan
AI-Build AuditA signed report within 48 hours: what is exposed, what you own, and the order to fix it in.Fixed price · 48 hoursAsk for the audit
FixThe report’s list, fixed for a set price by a set date. If we miss the target, the next week is on me.Fixed price and dateAsk about the fix
GuardA weekly automated scan, dependency and model updates, a monthly senior review, and one named person who answers.MonthlyAsk about Guard
Every 7Maps day is signed and chained to the day before.Verify in your browser