Skip to main content

Opinion

AI and cyberattacks: Why businesses must reassess security priorities

PHP2Shell, stolen customer data and manipulated refrigeration systems show which security work businesses need to reassess. An opinion by Julian Köhn.

Julian Köhn
|Read time: 4 minutes

An update will not fit the maintenance window. Replacing a legacy system would take too much work right now. These decisions have operational reasons. With an exploitable vulnerability, they leave an attack path open unless someone limits the remaining exposure.

Businesses need to reassess deferred security work. AI can reduce the effort specialists need to find and exploit vulnerabilities. A technically difficult flaw may therefore be exploited sooner than expected. Priorities based on the hope that exploitation will remain difficult need a different basis.

Waldbröl: Encrypted IT and stolen customer data

Stadtwerke Waldbröl reported encrypted parts of its IT on 21 October. According to the company, drinking water, wastewater and street lighting were unaffected. On 30 October, managing director Mirco Kujbida confirmed customer data theft to Oberberg-Aktuell. He said the forensic specialists hired by the company had confirmed the theft.

The publicly reported harm includes a loss of information confidentiality. Continued utility services do not make stolen customer data harmless. Reliable details of the entry point remain unpublished. The sources establish neither AI use nor specific failures to apply safeguards.

PHP2Shell changes the assessment of technically difficult flaws

The PHP Foundation describes an underlying flaw known since 2024. At that point, no concrete path to arbitrary code execution was known. Proposed fixes risked introducing other problems or breaking existing extensions. A small team had to weigh these drawbacks. Work repeatedly stalled. The Foundation identifies a structural problem with resources and decisions.

Wiz Research reports using AI in discovering and developing working exploits. During its research, the team adapted them to several applications within hours. It shows that previously demanding work can happen faster.

Palo Alto Networks reports attacks against internet-facing management interfaces of its products. It does not establish whether those attackers used AI.

The UK's NCSC assesses AI as an accelerator of existing attack techniques. Experienced actors can benefit in particular. The agency therefore expects greater pressure to release and install security updates faster.

For businesses, this changes a practical decision. An attacker's presumed effort is an uncertain justification for leaving an exposed system unchanged. Our guide to returning systems to service explains what to check for continued safe operation after PHP2Shell.

Security also covers equipment and physical access

On 2 November, Edeka Ernst in Reisbach had to dispose of much of its refrigerated stock. The operator confirmed manipulated refrigeration systems to BR. Affected equipment was disconnected from the internet. The report establishes neither a specific exploited CVE nor AI use.

Altered controls can make physical goods unusable. An inventory therefore needs equipment, maintenance access and responsible service providers. Our article on refrigeration attacks explains these dependencies.

Protecting these systems also means controlling physical access. Who may enter the equipment room? Which keys have been issued? How are visitors and external maintenance staff supervised? Secure remote access offers limited protection if an unauthorised person can make changes on site.

Deferral needs an accountable decision

Not every business can fix every vulnerability immediately. An unprepared change to running equipment can itself cause damage. The alternative is a reasoned decision about continued operation and interim safeguards.

Use your existing inventory. Start with a system whose failure or manipulation would seriously affect the business. Add the known flaw and affected activities to its risk record. Agree with the owner which available access paths you can restrict now and which change needs preparation.

Define when implementation should happen or which approval condition must be met first. A running contract or unavailable maintenance window does not establish how long the remaining risk is tolerable. Someone who can take responsibility for the business consequences needs to make that decision.

Then verify the result. For an update, check the actual installed versions. For a removed maintenance connection, check whether access is closed. Adding a measure to the record does not itself reduce risk.

Keep the inventory connected to decisions

You can start with existing lists. Keeping them consistent takes more work when owners change or the same equipment supports several processes. References and decisions still need to match.

In Kopexa, you prioritise outstanding security measures by the affected systems and their potential business impact. You can see who owns implementation and how far it has progressed. Configurable reviews with notifications remind you to reassess deferred decisions.

Take one deferred security measure and review its justification. If it depends on an attack being too complicated, require a current technical assessment.

Sources

  1. Stadtwerke Waldbröl: Notice of an IT security incident () [Accessed ]
  2. Oberberg-Aktuell: Stadtwerke Waldbröl extorted by a Russian hacking group () [Accessed ]
  3. PHP Foundation: Today's PHP Security Release, and How We're Strengthening PHP Security () [Accessed ]
  4. Wiz Research: PHP2Shell () [Accessed ]
  5. Palo Alto Networks: CVE-2026-109618 and CVE-2026-109619 () [Accessed ]
  6. NCSC Annual Review 2026: The impact of AI on cyber threat [Accessed ]
  7. BR24: Refrigeration cyberattack affects supermarket in Lower Bavaria () [Accessed ]