Drupal : contournement des contrôles d'accès — corrigée en 2.1.2

1. Vérifier si vous êtes concerné

   Versions ou systèmes touchés :

   <2.1.2

   drush status --field=drupal-version
   composer show drupal/core

2. Corriger

   Versions corrigées : 2.1.2.

   Mettre à jour le cœur ou le module concerné avec Composer, appliquer les mises à jour de base, vider les caches, sur chaque site.

   composer update "drupal/core-*" --with-all-dependencies
   composer update drupal/<module> --with-all-dependencies
   drush updatedb -y && drush cache:rebuild

3. En attendant le correctif

   Désactiver le module concerné (drush pm:uninstall <module>) si le correctif ne peut pas passer tout de suite, ou retirer la permission vulnérable aux rôles non administrateurs.

4. Contrôler

   drush status --field=drupal-version et composer show drupal/<module> doivent afficher la version corrigée.

   Rapport de statut Drupal (/admin/reports/status) sans alerte de sécurité.

Commandes indicatives (Debian ou Ubuntu) : à adapter à chaque serveur, après sauvegarde.

This module enables you to generate and serve WebP derivatives of image style images, overriding Drupal core's image style download controller to serve them. The module serves WebP image derivative responses with the HTTP header Cache-Control: public for all file schemes other than the private file system, including the temporary file system and access-controlled custom schemes. This can lead to some users getting cached versions of files with information they should not be able to access. For example, files may be cached by Varnish or a CDN. This vulnerability is mitigated by the fact that it only affects sites that serve image derivatives from a custom or temporary file scheme with access control, behind a shared cache that honors the Cache-Control header. Access checks are still enforced on requests that reach the site itself. An attacker would also need to know the path of a previously requested file still in cache. This is the same vulnerability class fixed in Drupal core by SA-CORE-2025-008 and SA-CORE-2026-010 ; the module's controller override reintroduced the behavior. Solution : Install the latest version: - If you use the ImageAPI Optimize WebP module 2.1.x, upgrade to ImageAPI Optimize WebP 2.1.2 - ImageAPI Optimize WebP 2.0.x only supports Drupal 10.1 and 10.2, which are end-of-life. It will not receive a security update and is no longer supported.