Close the critical vulnerability
Remote sources disabled, framework upgraded and the fix verified live on all three environments.

An events portal partly fed by automated collection, served by a modern front end, a business API and satellite services across three environments.
The assignment became critical when a remote code execution vulnerability, rated 9.5 out of 10, was published on the image optimiser of the framework in use.
The scope describes the decisions and the work actually carried out, without naming the organisation involved.
Remote sources disabled, framework upgraded and the fix verified live on all three environments.
Code analysis before the change: the site only used native images, so closing the feature had no functional effect.
Fingerprint comparison between servers and repository after a manual fix that had never been committed was found.
An uncommitted fix is now considered non-existent, to prevent any silent reintroduction.
Clients, brands, domains, addresses and identifying details are not published. The figures come from the logs, databases, clusters, repositories and control reports provided for these assignments. Security incidents are described without any reproducible exploitation path.
Describe the context, the existing systems and the expected result. We will propose the right level of intervention.