#010Learning1 min
How a flaw can expose customer data
The concrete path of a leak: one wrongly allowed request is often enough.
Hackaiz team · updated 19/11/2026

01The concrete path of a leak
A data leak rarely starts with a spectacular attack. Often one request that should never have been allowed is enough: asking for the full customer list instead of one’s own profile, or changing a number in an address to read someone else’s order. If the database does not check who is asking, it simply answers.
02The most frequent causes
These causes come up often in apps built quickly, with or without AI.
- 1A table readable by anyone because no access rule was written.
- 2An admin key placed in the site’s code.
- 3A server function that trusts the identifier sent by the browser.
- 4Files stored in a public space without anyone realizing.
03Consequences for your business
Exposed data can trigger notification duties depending on your country, a loss of customer trust and fraud. Severity depends on the data involved: an email address, payment information or health data do not call for the same response. If you are unsure of your obligations, consult legal counsel.
04Reduce the risk
Write an access rule for each table, keep secret keys on the server and check the user in every sensitive function. Then have these points examined: a Hackaiz report presents each issue with its evidence, masks secret values and lists what was not checked.
Frequently asked questions
Take the next step
Was this article helpful?