Drupal security updates, in plain English · Module

CSS Usage Analyzer

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

This module lets a design scanner send usage measurements to the site so administrators can see real page statistics.

Below is every security update for CSS Usage Analyzer 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.

CSS Usage Analyzer

Moderately critical · 12 sites report using it · SA-CONTRIB-2026-189 · on drupal.org · Week of 23 September 2026

Anyone without logging in could send fake design measurements to the site. They could add false statistics to the administrator reports. They could not view any private information.

  • Who could do thisAnyone visiting the site. No login needed.
  • Does it apply to youAny site using this 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 CSS Usage Analyzer to 1.0.2.

For developers: what the fix changed

The fix introduces a new permission in css_usage_analyzer.routing.yml to restrict access to the save endpoint. It also implements flood control and URL validation in the ajaxSave method of src/Controller/CssUsageAnalyzerController.php to prevent forged or repeated submissions.

Also in this release The release also adds an update hook and updates the README file to document the new permission.

1.0.1 to 1.0.2 2 commits, 6 files.

  • README.md +15 −2
  • css_usage_analyzer.install +7 −0
  • css_usage_analyzer.module +1 −1 fix
  • css_usage_analyzer.permissions.yml +5 −0 fix
  • css_usage_analyzer.routing.yml +6 −3 fix
  • src/Controller/CssUsageAnalyzerController.php +46 −0 fix

Full diff, 1.0.1 to 1.0.2

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 charities, membership bodies 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.