Maintainers finally have a tagged Drupal 12 build to put real projects against. Some compatibility work will need another pass, however, because the dependency target is not yet frozen.
...more
Critical ratings are only part of the triage. Project reach varies sharply, and one advisory requires administrators to clean stored data after updating.
...more
For multilingual Drupal teams, the key safeguard is control over what AI may refresh. Human-authored or human-edited translations stay untouched unless an overwrite is explicitly requested.
...more
Five Moderately Critical labels do not describe one kind of failure. Earlier Drupal disclosures show where payment, identity, and outbound-request risks recur, and where the similarities stop at the advisory classification.
...more
A contributed experiment can take years to become a supported core capability. PreviousNext’s history offers one view of the work sustained between those points.
...more
Repeated address entry and tracking updates add work after checkout. The release moves core MRW shipment tasks into the backend already used to manage orders.
...more
The same severity label does not mean the same exposure. Site maintainers need to distinguish administrator-dependent XSS from a permission-based field-editing bypass when assessing the two updates.
...more
A single advisory window can demand upgrades, removals, and tighter environment controls. The correct response depends on support status and exposure conditions, not the severity label alone.
...more
The batch presents three response paths to Drupal site teams: uninstall unsupported projects, patch active modules, and review where untrusted or generated content reaches the rendering layers.
...more
For Drupal teams using Layout Builder, the harder problem is often not creating inline blocks, but finding them after they leave the editor’s immediate view.
...more