AdobeAnalytics
The module lacks proper access controls for some of its advanced features. An ordinary account on the site could use this to run unwanted scripts. This could let them uncover hidden details or alter content on the site.
- Who could do thisOnly someone with a login on your site.
- Does it apply to youSites are affected if a user has the access right to add or edit content that uses the advanced features of the module.
- Has it been used in attacksNo sign of it.
- How urgentDrupal rates this moderately critical. Include it in your next routine update, within the month.
Tell your developerUpdate AdobeAnalytics to 8.x-1.1.
For developers: what the fix changed
The fix implements `hook_entity_field_access()` in `adobe_analytics.module` and `src/Hook/AdobeAnalyticsHooks.php` to restrict edit access for the `adobe_analytics` field type to users with the `administer adobe analytics configuration` permission, preventing unauthorised users from injecting arbitrary JavaScript.
Also in this release The release also adds GitLab CI configuration, updates core version requirements for Drupal 11 and 12, and converts hooks to use the new object-oriented hook attributes.
.cspell.json+36 −0.gitignore+1 −0.gitlab-ci.yml+67 −0README.md+5 −5adobe_analytics.info.yml+1 −1adobe_analytics.module+25 −22 fixadobe_analytics.services.yml+6 −2src/Form/AdobeAnalyticsAdminSettings.php+4 −4src/Hook/AdobeAnalyticsHooks.php+95 −0 fixsrc/Plugin/Field/FieldWidget/AdobeAnalyticsWidget.php+4 −4src/TrackingMatcher/TrackingMatcherInterface.php+3 −3src/VariableFormatter.php+3 −4