Drupal security updates, in plain English · Module

DXPR Builder: The Best Editing (AI) Experience for Drupal

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

This module provides a visual tool and artificial intelligence features for building pages on the website.

Below is every security update for DXPR Builder: The Best Editing (AI) Experience for Drupal 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.

DXPR Builder: The Best Editing (AI) Experience for Drupal

Moderately critical · 907 sites report using it · SA-CONTRIB-2026-112 · on drupal.org · Week of 26 August 2026

Anyone without logging in could look at the background settings of a page and find the secret digital key used for the artificial intelligence services. This would allow them to read private subscription details. They could not change any settings or content.

  • Who could do thisAnyone visiting the site. No login needed.
  • Does it apply to youA site is affected if it has the artificial intelligence features turned on and configured with a secret key.
  • 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 DXPR Builder: The Best Editing (AI) Experience for Drupal to 2.8.1.

For developers: what the fix changed

Wraps the inclusion of AI settings and the API key in an `if ($enable_editor)` check within `DxprBuilderFormatter.php` to prevent exposing credentials to non-editors, and adds the `user.roles:authenticated` cache context.

Also in this release Fixed image style selection logic, added file usage tracking for uploaded files, and resolved various PHPStan warnings.

2.8.0 to 2.8.1 2 commits, 14 files.

  • dxpr_builder.info.yml +1 −1
  • dxpr_builder.install +0 −2
  • dxpr_builder/dxpr_frontend.min.js +0 −0
  • js/image-select.js +6 −0
  • js/image-utils.js +4 −4
  • modules/dxpr_builder_block/dxpr_builder_block.info.yml +1 −1
  • modules/dxpr_builder_page/dxpr_builder_page.info.yml +1 −1
  • src/Controller/AjaxController.php +0 −2
  • src/Controller/UploadFileController.php +9 −0
  • src/Form/DxprBuilderSettingsForm.php +0 −1
  • src/Form/DxprBuilderUserTemplateForm.php +2 −1
  • src/Plugin/Field/FieldFormatter/DxprBuilderFormatter.php +184 −184 fix

Full diff, 2.8.0 to 2.8.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.