Cleverbase says it updated its IT systems so that the affected eMudhra certificates are no longer trusted.
Two serious vulnerabilities in IT systems: what is going on and what you can do ↗
What happened
- Cleverbase says one of its systems, with limited impact on its services, runs on PHP and was switched off until the security update is installed.
- Cleverbase states that it is investigating the impact on its suppliers' systems.
Why it matters to Signicat
- Cleverbase's public response is a security-incident communication about certificate trust and PHP exposure, not a product or commercial move.
- Cleverbase's statement that its identification, login and signing services are not at increased risk is vendor-stated and not independently verified.
Evidence from the source (4 quotes)
- “One system, with limited impact on our services, runs on PHP. As a precaution, we have switched that system off until the security update has been installed.” source ↗
- “In addition, we are investigating the impact on our suppliers' systems, and taking measures where needed.” source ↗
- “As soon as the news broke, Cleverbase took immediate action.” source ↗
- “As a result, our services for identification, logging in and signing are not at increased risk.” source ↗
eSign trust servicesSecurity incidentBenelux
3 of 3 facts verified against the source · confidence high · claude-haiku-5-5