DRUPAL-CONTRIB-2021-025 json
The *Admin Toolbar* (`admin_toolbar`) module extends the default toolbar provided by Drupal Core with various features facilitating day-to-…
published 5y ago modified 2mo ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
The *Admin Toolbar* (`admin_toolbar`) module extends the default toolbar provided by Drupal Core with various features facilitating day-to-day editorial and administrative work.
The *Admin Toolbar Search* sub-module of this module
* doesn't sanitize user input in certain cases, which leads to a Cross-Site-Scripting (XSS) vulnerability. An attacker that can create or edit certain entities, entity bundles or entity types may be able to exploit one or more Cross-Site-Scripting (XSS) vulnerabilities to target users with access to the *Admin Toolbar Search* search box, including site admins with privileged access. * doesn't properly check access in certain cases, which may result in an information disclosure vulnerability of entity type and bundle labels.
The vulnerability is mitigated by the facts, that:
* the *Admin Toolbar Search* sub-module must be enabled. * an attacker must have one of several permissions, of which at least some are commonly only assigned to either editors, site builders or administrators. * a targeted account must have permission to use the search box provided by the *Admin Toolbar Search* sub-module.
Patch / fix
- packagist drupal/admin_toolbar 2.5.0
Is DRUPAL-CONTRIB-2021-025 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | drupal/admin_toolbar | <2.5.0 >=3.0.0, <=3.0.0 >=3.0.1, <=3.0.1 |
2.5.0 |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.