Two adjacent metal lockers, one slightly open to reveal a violet glow.

Secure

When one account can read another's data

The web's number one vulnerability is not a virus: it is one account reading another's data.

Published October 11, 2026Read in French

In May 2019, one of the largest insurers in the United States, First American Financial, left approximately 885 million documents accessible: bank statements, social security numbers, driver's licenses, mortgage deeds, wire transfer receipts. No sophisticated hacking. To view another customer's document, all it took was changing a number in the page address. No password, no break-in. A single digit changed in a URL (source: SecurityWeek, Krebs on Security, May 2019).

The number one flaw is not the one you imagine

We picture a cyberattack as malicious code forcing a door open. The reality is more mundane and more serious. In its 2021 ranking, OWASP (the world reference in application security) places broken access control first in its Top 10. The figures: 94% of applications tested showed some form of this flaw, with 318,487 occurrences recorded, the highest total of any category (source: OWASP Top 10 2021, A01).

Translated into business terms: in nearly all audited applications, a user could, in one way or another, reach what did not belong to them.

What this means for your application

The question is not "is my site protected from hackers." It is: if two of my customers are logged in at the same time, can account A see account B's data? Three situations are enough to open the breach:

  • an order, invoice, or file identifier that can be guessed in the URL,
  • an access rule checked on the interface side but not on the server side (anyone who knows the direct address bypasses it),
  • an "administrator" or "premium" role that a user can assign to themselves by modifying a request.

None of these three triggers an alert. The application works normally. It leaks silently.

Why a surface test is not enough

An automated scan detects an expired certificate or an outdated component. It does not know that your "order 1042" belongs to Mrs. Durand and not to the person currently logged in. Verifying real access between accounts requires creating two accounts and attempting, from one, to reach the other's data. It is a manual, targeted test that free tools do not perform.

What I recommend

Start with the free test: it gives you a score and an overview of your exposed surface. But for the one question that truly matters, "who can access my customers' data," you need the commissioned audit: I create the accounts, I attempt cross-account access, and I hand you the proof, with screenshots to back it up.

Sources