PHP flaw prompts global website shutdowns

Thursday, 22 October 2026

Illustrative photo: Black laptop computer turned on on table.

Photo by James Harrison on Unsplash

Illustrative photo: Black laptop computer turned on on table.

Lesson plan for about 60 minutes of class time

Interactive lesson: about 15–20 minutes

Warm-up

  1. Have you ever seen a favourite website go offline? What happened?
  2. How quickly do you usually install updates on your devices? Why?
  3. What online services do you rely on most each day?

Vocabulary

vulnerability
a weakness in a system that attackers can use
patch
a software update that fixes a problem or adds a small change
exploit
to use a weakness to attack or enter a system
precaution
an action taken to prevent possible danger or harm
database
an organised collection of data stored on a computer
reverse-engineer
to analyse something to figure out how it works
compromise
a break-in that damages the security of a system
maintain
to keep something working by checking and updating it

Reading

0:00 / --:--

Websites around the world were taken offline after a serious vulnerability was revealed in PHP, the computer language used by almost 70% of websites. Governments temporarily took down Belgian, Dutch, Finnish, French and German sites as a precaution while teams applied a patch. National security agencies in the US and UK warned that the flaw could let attackers reach a server's file system or database, and told organisations unable to patch immediately to take systems offline.

Major platforms depend on PHP. WordPress runs on it; Wikipedia and Slack use it; and Facebook has historically used it. The Wikimedia Foundation temporarily shut several systems to apply fixes. Experts fear hackers will try to exploit the bug quickly because AI tools can reverse-engineer it. Costin Raiu said a "race to exploit" could lead to mass compromise of vulnerable web servers. Prof Alan Woodward warned that poorly maintained websites may remain exposed for months. Research groups including OpenAI, Calif and Wiz said they helped identify the flaw.

Original source

Adapted with AI assistance from the original article. Checked by automated tests before publishing; mistakes found later are corrected. Spotted one? Tell us.

Comprehension

  1. What computer language is at the centre of the flaw?
  2. Roughly what share of websites use this language?
  3. Which countries took some government sites offline as a precaution?
  4. What did security agencies advise if organisations could not patch at once?
  5. Why do experts expect fast attempts to exploit the bug?

Grammar focus

Future perfect

Use will have + past participle to show an action finished before a future time or event. Common signals: by + time/date, by then, by the time + clause, within + period, before + event. (Examples constructed.)

  • By tonight, teams will have applied emergency patches.
  • Within days, attackers will have found weak sites.

Practise this grammar: Future perfect (B2)

Grammar exercise

Complete each sentence with the future perfect form.

  1. By tomorrow, many admins (secure) ___ their servers.
  2. Before patches arrive, bots (scan) ___ the web.
  3. Within 48 hours, vulnerable pages (be) ___ taken offline.
  4. By then, most site owners (update) ___ their software.
  5. By the time alerts go out, teams (identify) ___ attempts.

Discussion

  1. Was taking sites offline a good precaution in this case? Why or why not?
  2. How should organisations prioritise patching older, less maintained systems?
  3. Does AI make cyber risks grow faster than defences can? Explain.
  4. Which online services would you miss most if they went offline for a day?

For teachers

Timing

  • warm-up · 8-10 minutes
  • vocabulary · 10 minutes
  • reading · 12-15 minutes
  • comprehension · 10 minutes
  • grammar · 8-10 minutes
  • discussion · 10-12 minutes

Teacher's notes

  • Pre-teach or check: PHP (as a scripting language), patch, exploit, database, precaution; highlight pronounceable chunks in multi-word items like reverse-engineer and file system.
  • For the reading, set a gist task (Who took sites down and why?). Then scan for details (the 70% figure, named countries, agency advice). Pair-check before whole-class feedback. No sensitive personal topics are required; keep discussion focused on services, choices and risk management.
  • Differentiate: stronger learners summarise the race-to-exploit idea; others underline evidence for each risk. As an extension, have pairs list three concrete steps a small organisation could take this week to improve maintenance and patching.

Answers

Show answers

Comprehension

  1. PHP.
  2. Almost 70% of websites.
  3. The Belgian, Dutch, Finnish, French and German governments.
  4. Take systems offline until they can apply the patch.
  5. AI tools can reverse-engineer the bug, creating a race to exploit it.

Grammar exercise

  1. By tomorrow, many admins (secure) ___ their servers. will have secured
  2. Before patches arrive, bots (scan) ___ the web. will have scanned
  3. Within 48 hours, vulnerable pages (be) ___ taken offline. will have been
  4. By then, most site owners (update) ___ their software. will have updated
  5. By the time alerts go out, teams (identify) ___ attempts. will have identified

The printable PDF has the same notes and answers, laid out for class.

Start Interactive Lesson

Vocabulary, reading, and exercises with instant feedback

Spotted a mistake in this lesson? Tell us.