A remote code execution vulnerability exists within the Field UI module in Drupal core. The vulnerability is not directly exploitable with core alone, but mult...

A flaw in Drupal core's Field UI module can let an attacker run code on the server. Core alone is not directly exploitable, but contributed modules can expose exploit paths, at least one of which needs no authentication. Custom code may also expose the vulnerable functionality.

Look for drupal/core and its version in composer.lock. The advisory does not give affected version ranges; it lists fixes in 10.6.19, 11.3.19, 11.4.10 and 12.0.0-beta2. Check whether the core Field UI module (field_ui) is installed and whether contributed modules or custom code expose its vulnerable functionality. The advisory does not identify which contributed modules are involved.

Uninstall the core Field UI module (field_ui) to protect the site while updating. Drupal Steward protects sites using it from some known attack vectors, but not all possible exploits, so those sites should still upgrade in the near future.

A remote code execution vulnerability exists within the Field UI module in Drupal core.

The vulnerability is not directly exploitable with core alone, but multiple serious exploit paths exist with contributed modules. At least one known exploit path does not require authentication. Custom code may also expose the vulnerable functionality.

The vulnerability can be mitigated by uninstalling the core Field UI module (field_ui), which will provide protection while sites are updated.

Drupal Steward protection:

This issue is being protected by Drupal Steward. Sites that use Drupal Steward are already protected from some known attack vectors, but the protection offered will not cover all possible exploits. Sites should upgrade in the near future in case additional attack vectors are discovered.