Security Update – PHP Vulnerability

We are aware of the recent critical PHP security vulnerabilities highlighted by the National Cyber Security Centre (NCSC) on 21st October 2026.

We would like to reassure customers that our main platforms, 4Matrix Cloud and 4Matrix Fusion, do not use PHP and are therefore not directly affected by these vulnerabilities.

PHP is used within some of our supporting systems, including our customer support ticketing and billing systems. Our desktop application also communicates with our sales system for licence verification. These systems do not store customers' payment details or sensitive information as part of the licence verification process.

We have been in contact with our hosting provider, Krystal, who has confirmed that the necessary security fixes have been applied to address the reported vulnerabilities.

No action is required from our customers in relation to this advisory.

We take the security of our systems and customer information seriously and will continue to monitor security developments and work with our hosting provider to maintain appropriate protections.

Pupil Premium Numbers Do Not Match Between Arbor and 4Matrix

You may find that the number of Pupil Premium students in 4Matrix does not match the number shown in Arbor. This can happen when Arbor has not provided a valid start date for the student's Pupil Premium Eligible status.

4Matrix uses Arbor's Pupil Premium Eligible field to identify Pupil Premium students.

This is a derived field in Arbor, based on information such as:

  • Free School Meals (FSM) history (Ever6)
  • Looked After Child (LAC) / In Care history
  • Service Child history

For affected students, the Pupil Premium Eligible start date may show as "Ongoing" instead of a specific date, as may one or more of the fields that this is derived from.

This can affect Desktop and Cloud extracts differently:

  • Desktop: the student may be imported as NOT Pupil Premium eligible.
  • Cloud: the student may be imported as Pupil Premium eligible, but with a demographic row dated from the import date. This may result in an inaccurate historical record.

Solution:

First, check the affected student's profile in Arbor:

  1. Open the student's profile.
  2. Go to Derived Indicators.
  3. Find Pupil Premium Eligible.
  4. Check the start date.

If the start date is "Ongoing", check the student's underlying eligibility history.

LAC or Service Child history

If the student has LAC or Service Child history, make sure the relevant history has a valid start date.

Updating the start date, or deleting and re-entering the history with the correct date, will cause Arbor to recalculate the Pupil Premium Eligible start date.

FSM history

FSM-related cases can be more complicated due to changes to Arbor's FSM system and may result in the Ever 6 field having a 'ongoing' start date too. If the issue relates to FSM history fixing this will also resolve the issue.

Once corrected on Arbor, run the 4Matrix extract again.

When to Contact Arbor

Contact Arbor Support if:

  • The Pupil Premium Eligible start date shows as "Ongoing"
  • The student's FSM history appears correct, but the Pupil Premium Eligible start date is missing or incorrect.
  • You are unsure how to correct the underlying FSM history.
  • The issue continues after correcting the relevant student history.

Ask Arbor to investigate why the Pupil Premium Eligible start date has not been generated correctly and whether they can correct the underlying data.

Possible Arbor FSM Changes

We believe this issue may be related to recent changes in Arbor's FSM system, including the automatic move to FSM Targeted. Arbor should be able to confirm whether these changes are responsible for the issue and advise on the appropriate fix.