Skip to content
Business Agile
← Work
Web · Corporate foundation, food and health · 2017-2018

Fondation Nestlé France

Taking over an inherited site: twenty-eight holes closed and a written diagnosis.

Key figures

vulnerabilities closed, core and plugins28
outdated plugins handled4
written report delivered at the end1

Fondation Nestlé France had a WordPress site built by an agency that no longer followed it. Two problems arrived at once: the editorial team could no longer update its media, and the group's security service had just reported a hole in the WordPress core. The engagement was brought to me by the Skilld agency, which I worked with regularly, and I ran it directly.

The project in detail

The editorial blocker came from a plugin, Magic Fields 2, that the original agency had used to customise post types. Updating it fixed the fault, but the diagnosis did not stop there: that plugin had been pulled from the official WordPress repository, which made its fixes far harder to get. A site whose central part is no longer distributed by its supplier is a site whose next failure will have no fix.

On the security side the scan identified fourteen vulnerabilities in the core, and fourteen more spread across four plugins that had not been updated in years, some several major versions behind. Moving the core to the latest stable version closed the hole flagged by the group's security service and most of the others. The plugins were dealt with one by one.

I also worked inside the theme, replacing PHP functions that had become obsolete. That is the kind of fix you have to make and at the same time have to flag as a symptom: swapping a function for a newer one gets you through the day, but repeated over years it produces code nobody can pick up.

The engagement ended with a written report rather than a closing message. It listed what had been fixed, and above all two reasoned recommendations: replace Magic Fields 2 with Advanced Custom Fields, a plugin with the same purpose but maintained by a company that has made it its flagship product, and consider a technical rebuild of the theme. A technical rebuild changes neither the visuals nor the features offered to visitors, but it allows several decaying plugins to be removed and lastingly reduces maintenance time and attack surface.

This is the shape of all my takeovers of existing work: fix what blocks, close what is open, then say in writing what remains to be decided, with the reasons.

What was done

  1. 01

    Fourteen vulnerabilities closed in the WordPress core

  2. 02

    Fourteen more handled across four outdated plugins

  3. 03

    Hole reported by the group's security service closed

  4. 04

    Media update blocker diagnosed and lifted

  5. 05

    Obsolete PHP functions replaced in the theme

  6. 06

    Written intervention report with reasoned recommendations

Frequently asked questions

What do you do with a site inherited from an agency that no longer follows it?

You start by measuring. On the Fondation Nestlé France site, the scan found twenty-eight vulnerabilities across the core and the plugins. You then restore the security level, fix what blocks the teams, and hand over a written assessment so the client decides what comes next with full knowledge.

Why is a plugin pulled from the official repository a risk?

Because its fixes stop arriving through the normal channel. Magic Fields 2 was the part carrying the site's custom post types: updating it unblocked the situation, but the recommendation was to replace it with an actively maintained plugin.

Does a technical rebuild force a design change?

No, and that is its value. It replaces the theme's code without touching the visuals or the features offered to visitors. The benefit is elsewhere: fewer decaying plugins, less attack surface and maintenance time that drops for good.

Other work

A project? Let's talk this week.

A short brief, an answer within 48 hours, a firm estimate after scoping.

Describe my project