Drupal this week announced software updates that resolve a total of four vulnerabilities in Drupal core and three plugins, and which could lead to unauthorized access to data.
The Drupal core issue exists because the Media Library module does not perform proper checks on entity access in some cases, which could allow users who can edit content to view metadata about media items that they should not have access to.
An identical issue impacts the Media Library Form API Element plugin, which supports the use of the media library in custom forms, without having to use the Media Library Widget.
According to Drupal, both vulnerabilities are “mitigated by the fact that the inaccessible media will only be visible to users who can already edit content that includes a media reference field”.
The third flaw, which was patched in the Media Library Block plugin, which supports the rendering of media entities in a block, has a similar root cause: improper check of media access in some circumstances.
The vulnerability could allow users to see media items without authorization, provided that a block containing restricted media is placed on a page. To mitigate the bug, administrators can remove blocks referencing media items with access restrictions.
The fourth vulnerability was identified in the Entity Browser plugin, which enables users to “select entities from entity reference fields using a custom browser widget”.
Lack of proper entity access checks in some cases could allow users who have access to edit content to view entity metadata without authorization. Only users who can edit content using Entity Browser would be able to view the metadata.
The issues were resolved with the release of Drupal versions 10.0.2, 9.5.2, and 9.4.10, Media Library Form API Element version 2.0.6, Media Library Block version 1.0.4, and Entity Browser version 8.x-2.9.
Drupal assessed these vulnerabilities with a severity rating of ‘moderately critical’, which is roughly the equivalent of ‘medium severity’. More information on the resolved issues can be found on Drupal’s product security page.