Chargemap data breach: what an "old interface" can cost your business
One forgotten old entry point was enough to drain account data. The good news: the same habits also protect a small website.

Introduction
In mid-November, Chargemap, the charging app for electric cars, warned its users about a data theft. The attack took place on November 8, was detected on the 10th, the flaw was fixed on the 12th and the CNIL (the French data protection authority) was notified on the 13th. According to the company, the hacker got in through an "old technical interface".
I don't know the technical details, and Chargemap has not made them public. But that phrase sums up one of the most common causes of data leaks, for large and small companies alike: a piece of the system that is no longer used, no longer monitored, and yet still connected to the database.
What leaked, and what was protected
According to information published by Next and ITdaily, the data affected included: email address, username, date of last login, subscription status and, for those who had provided them, name, phone number, date of birth or profile picture.
On the other hand, bank details, invoices and charging history were not affected. And above all, passwords were only stored in hashed form: the hacker obtained a fingerprint, not the password itself. Only accounts inactive since 2019 still used a weaker format.
This detail shows two things: good practices really do limit the damage, and anything that ages without maintenance becomes the weak link.
The real risk: what you've forgotten
On the websites and apps I take over, I often find the same "old interfaces":
- an API from the old version of the mobile app, still online "just in case";
- a test or staging subdomain connected to the real database;
- a back office installed five years ago and never updated;
- WordPress plugins that are deactivated but still present on the server;
- administrator accounts of former contractors that still work.
Nobody looks at them, so nobody notices they are vulnerable. Hackers' bots, on the other hand, scan everything constantly.
5 habits to adopt this week
- Take inventory. List everything that is online: domains, subdomains, APIs, back offices, connected tools. Whatever is no longer used should be shut down, not just "hidden".
- Update. CMS, plugins, frameworks, server: most attacks exploit flaws already fixed by an update that nobody installed.
- Check how passwords are stored. They must be hashed with a modern algorithm (bcrypt, argon2), never in plain text or MD5.
- Keep only what's necessary. Data you don't collect can't leak. Also delete old data that is no longer useful.
- Prepare for what comes next. Tested backups, access logs enabled, and a simple procedure: who to notify, how to inform customers, when to report to the CNIL (72 hours in Europe).
And if you're a Chargemap user
Change your password, and above all those you reuse elsewhere, starting with your email account. Be wary of emails, texts or calls claiming to be from Chargemap and asking for information: this is scammers' favorite moment.
Need an outside perspective?
When I take over a website or an app, I always start with this kind of audit: what is exposed, what is out of date, what can be shut down. If you have doubts about your site, write to me: we'll look together at where to start.
Comments0
No comments yet. Be the first to share your thoughts.
