Drupal security updates, in plain English · Module

Smart Content

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

This module shows different content blocks to visitors based on their browser settings.

Below is every security update for Smart Content 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.

Smart Content

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

Anyone without logging in could view restricted content blocks by asking the server for them directly. They could see hidden text meant for other users. They could not alter any information on the site.

  • Who could do thisAnyone visiting the site. No login needed.
  • Does it apply to youThis applies if a site has placed a restricted block inside a display blocks reaction.
  • 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 Smart Content to 3.2.1.

For developers: what the fix changed

The fix updates the `DisplayBlocks` reaction plugin to correctly call `isAllowed()` on the block access result object in `modules/smart_content_block/src/Plugin/smart_content/Reaction/DisplayBlocks.php`, rather than just checking if the object itself evaluates to true.

Also in this release The release also includes Drupal 11 compatibility updates and PHP 8.2 deprecation fixes.

3.1.0 to 3.2.1 4 commits, 18 files including 5 tests.

  • modules/smart_content_block/smart_content_block.info.yml +1 −1
  • modules/smart_content_block/src/EventSubscriber/LayoutBuilderComponentRenderArray.php +1 −1
  • modules/smart_content_block/src/Plugin/smart_content/Reaction/DisplayBlocks.php +2 −1 fix
  • modules/smart_content_browser/smart_content_browser.info.yml +1 −1
  • smart_content.info.yml +1 −1
  • src/Condition/ConditionTypeConfigurableBase.php +2 −1
  • src/Condition/ConditionsHelperTrait.php +1 −1
  • src/Condition/Type/ConditionTypeBase.php +14 −0
  • src/Condition/Type/ConditionTypeInterface.php +9 −0
  • src/Decision/DecisionBase.php +1 −1
  • src/Plugin/DataType/DecisionData.php +16 −0
  • src/Plugin/Field/FieldType/DecisionItem.php +2 −1

Full diff, 3.1.0 to 3.2.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 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.