Drupal security updates, in plain English · Module

AdobeAnalytics

9 sites report using it · on drupal.org · 1 security update explained here

This module connects a website to Adobe analytics software to track visitor activity.

Below is every security update for AdobeAnalytics that this site has covered, newest first. Each one says who could exploit it, whether it applies to your site, how urgent it is, and what to tell your developer. If your site uses this module and you are not sure which version, that is the first question to ask whoever looks after it.

AdobeAnalytics

Moderately critical · 9 sites report using it · SA-CONTRIB-2026-311 · on drupal.org · Week of 4 November 2026

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.

8.x-1.0 to 8.x-1.1 4 commits, 22 files including 9 tests.

  • .cspell.json +36 −0
  • .gitignore +1 −0
  • .gitlab-ci.yml +67 −0
  • README.md +5 −5
  • adobe_analytics.info.yml +1 −1
  • adobe_analytics.module +25 −22 fix
  • adobe_analytics.services.yml +6 −2
  • src/Form/AdobeAnalyticsAdminSettings.php +4 −4
  • src/Hook/AdobeAnalyticsHooks.php +95 −0 fix
  • src/Plugin/Field/FieldWidget/AdobeAnalyticsWidget.php +4 −4
  • src/TrackingMatcher/TrackingMatcherInterface.php +3 −3
  • src/VariableFormatter.php +3 −4

Full diff, 8.x-1.0 to 8.x-1.1

The comparison is against the release immediately before the fix. If your site is on an older release, more will have changed.

Not sure what your site is running?

Send me your Drupal site's address.

I'll tell you what I can see from outside, what the Drupal 10 end of life on 9 December means for it, and what it would cost to have me keep it patched. There's no charge for that and no obligation. peter@peterbrady.co.uk


Get in touch

Tell me who you are, what your organisation does, and what you need. That might be a Drupal site that needs looking after, an upgrade to get done before December, or an agency that needs Drupal cover.

If I can help, I'll say so and suggest a call. If I can't, I'll tell you straight away rather than waste your time.

peter@peterbrady.co.uk

For context: I work mainly with UK membership bodies, charities and research organisations, and with the agencies that look after their websites. Not recruiters.

Or start smaller and connect with me on LinkedIn. That's where I post what I find digging around in charity and grants data, and where the free tools turn up first.