Digital security

Fake PHP updates and leaked data: phishing that looks genuine

E
ElaraTeq
Cover: fake PHP updates and leaked data, phishing that looks genuine according to the NCSC; glass panels with email, alert, website, padlock and document over a night lake

The NCSC reports emails using the critical PHP flaw to steal website panel logins, and phishing with names, addresses and OASI numbers taken from a data breach. What to do in the office and what the FADP requires.

The most effective phishing emails are not the badly written ones, but those that refer to a real event or contain real data. In its week 46 review, published on 17 November 2026, the National Cyber Security Centre (NCSC) describes two recent cases: fake update notices linked to the critical PHP vulnerability, and personalised messages built with data from an earlier data breach.

For a Ticino SME with a website, an administration panel or a customer database, both cases are a practical reminder.

Case 1: the PHP flaw becomes a pretext

On 21 October 2026 the PHP project fixed two critical vulnerabilities (CVE-2026-109618 and CVE-2026-109619) with versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35 (official PHP advisory). The same day the NCSC published a warning urging immediate updates. On 12 November Check Point reported real attacks against its own unpatched gateways, observed between 30 October and 4 November. On our blog we covered the flaw and what to do with your website in the post on the PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619.

Now the attention around the topic is being exploited in a different way. According to the NCSC, targeted emails refer to the PHP vulnerability and ask recipients to log in to the control panel to install a supposed update or read more. The link leads to a phishing page. Anyone who enters their login details there hands the attackers access to the website’s administration tool, which can then be modified or taken over completely.

The message works because the problem is real and widely reported: people who run a website know there is an update to install and tend to trust it. But updates are installed through the official channels of the vendor, the hosting provider or the administration procedures already in place, not through a link received by email.

Case 2: leaked data that makes the scam credible

The second case concerns a Swiss company that provides employment and management services for domestic helpers. On 7 October 2026 it reported a data breach and warned those affected about possible misuse. On 24 October phishing emails were sent in the company’s name containing the recipients’ names, addresses and OASI (AHV) numbers. The link opened a form already filled in with these details and asked for credit card data, including the security code.

The NCSC stresses that leaked data can be used months or even years later and that, after recent cases in which OASI numbers and other personal data were stolen, such data is likely to be used increasingly in emails, text messages and phone calls. A correct name, address or number is therefore no proof that a message is genuine.

What to do in the office

  1. Panels from bookmarks only. Always open the hosting, CMS or online shop panel from the saved address, never from a link in an email or text message, even if the message seems to come from your provider.
  2. Know who updates PHP. Clarify in writing whether server updates are the job of the hosting provider, an agency or your own team, and how you are informed. Any message outside this pattern should be checked by calling a number you already know.
  3. Two-factor authentication. Enable it on the hosting panel, CMS, email and domain registrar: a stolen password alone is then no longer enough. See the NCSC’s five levels of login security.
  4. Be wary of news-driven urgency. Tell staff and family members that widely discussed vulnerabilities and recent data breaches are a common pretext for phishing.
  5. Correct personal data is not enough. Anyone asking for a credit card, security code, password or IBAN via a link should be verified on an independent channel, as with the fake commercial register and tax administration emails.
  6. If you entered login details. Change the password immediately on the real site, revoke active sessions, check administrator accounts, files and site content, and inform whoever manages your hosting.

If the data breach is in your company

The second case also shows what happens after an incident. Under Article 24 of the Swiss Federal Act on Data Protection (FADP), a data security breach that is likely to result in a high risk for the persons concerned must be reported to the FDPIC as soon as possible; the persons concerned must be informed when this is necessary for their protection or if the FDPIC requests it. The FDPIC guidelines help assess the case. In the notice to customers it helps to state clearly which data is affected, how the company will contact them and which requests it will never make.

Suspicious emails can be reported through the NCSC reporting form or on antiphishing.ch; if there is financial damage, a complaint should be filed with the cantonal police. For most SMEs reporting to the NCSC is voluntary; operators of critical infrastructure, by contrast, have a reporting obligation for cyberattacks within 24 hours.

Our approach

ElaraTeq Sagl manages websites and servers for Ticino SMEs with planned updates communicated through agreed channels, two-factor authentication on logins and hosting in Switzerland (hosting). For CMS updates see also the WordPress CVE-2026-119977 case. To review logins, panels and procedures you can ask for consulting or contact us.

Sources

Tags: #phishing #PHP #CVE-2026-109618 #CVE-2026-109619 #fuga di dati #numero AVS #UFCS #nLPD #PMI
Share:

Want to Work With Us?

Let's discuss how we can help bring your vision to life.

Get in Touch