Imagine a car manufacturer issues a recall. Important news, and if you drive that brand, you should get to the garage quickly. But if you drive a different brand, you just keep driving.
That is how it works with the PHP vulnerability in today's news. PHP is a widely used programming language for websites. Organisations that use PHP need to install an update quickly; the Dutch National Cyber Security Centre is urging them to do so. Laadloon does not use PHP. So we don't need to go to the garage.
Do I need to do anything?
No. You don't need to change your password or reconnect anything.
Do my charging sessions still count?
Yes. Every kWh you charge at home comes in and is registered as usual. Your payout is on schedule.
What if my charger brand is affected?
Then your latest charging sessions may take a little longer to appear in your customer portal. As soon as their system is reachable again, we will fetch them.
Will Laadloon email me about this?
No, and that may be the biggest risk today. Around news like this, scammers send official-looking emails: "Log in again as a precaution" or "Confirm your bank details". We don't send emails like that. Received one in our name anyway? Don't click the link: go to app.laadloon.nl yourself and forward the email to vragen@laadloon.nl.
How do we keep things secure?
A vulnerability like this can affect any organisation, in any software. That is why we follow the security notices for our own software and update quickly when needed. Today there was nothing to update.
Any other questions? Email us at vragen@laadloon.nl.