Drupal security updates, in plain English · Module

Block Attributes

2,810 sites report using it · on drupal.org · 1 security update explained here

This module allows you to define custom attributes for a block.

Below is every security update for Block Attributes 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.

Block Attributes

Moderately critical · 2,810 sites report using it · SA-CONTRIB-2026-232 · on drupal.org · Week of 21 October 2026

The module does not sufficiently sanitise attributes against malicious scripts. An administrator account could view restricted information and alter or add new data through these custom attributes.

  • Who could do thisOnly someone with an administrator login.
  • Does it apply to youAn attacker must have the administer blocks access right.
  • 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 Block Attributes to 2.1.0.

For developers: what the fix changed

The fix introduces strict validation for attribute names using a regular expression in BlockAttributesChecker::isAttributeAllowed and adds a filterAttributeValues method to ensure only safe attributes are rendered. It also updates ConfigForm::validateForm to enforce these rules during configuration and adds an update hook in block_attributes.install to clean up existing invalid attributes.

Also in this release Added a cspell project words file to fix a misspelt word.

2.0.1 to 2.1.0 2 commits, 5 files.

  • .cspell-project-words.txt +1 −0
  • block_attributes.install +50 −0 fix
  • block_attributes.module +23 −4 fix
  • src/BlockAttributesChecker.php +59 −3 fix
  • src/Form/ConfigForm.php +14 −2 fix

Full diff, 2.0.1 to 2.1.0

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.