Drupal security updates, in plain English · Module

AI Translate

5,948 sites report using it · on drupal.org · 1 security update explained here

This module automatically translates pieces of content.

Below is every security update for AI Translate 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.

AI Translate

Moderately critical · 5,948 sites report using it · SA-CONTRIB-2026-121 · on drupal.org · Week of 2 September 2026

The module does not properly check access rights on related fields or referenced items during translation. A user with an ordinary account could translate items they should not have access to. They could not read or update the affected items in other ways.

  • Who could do thisOnly someone with a login on your site.
  • 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 AI Translate to 1.3.2 or 1.4.1, whichever branch you are on.

For developers: what the fix changed

The fix replaces the generic permission check on the translation route with a custom access callback in `AiTranslateController::checkAccess` to ensure the user has update access to the entity and translation create access. It also adds field-level view access checks in `TextExtractor` and referenced entity view and update access checks in `ReferenceFieldExtractor`.

Also in this release The release also adds translation result caching, support for translating the 'description' field in custom menu link content, GitLab CI configuration, and documentation.

1.3.1 to 1.3.2 11 commits, 44 files including 8 tests.

  • .cspell-project-words.txt +11 −0
  • .gitlab-ci.yml +73 −0
  • .gitlab/issue_templates/bug_report.md +69 −0
  • .gitlab/issue_templates/feature_request.md +48 −0
  • .gitlab/issue_templates/plan.md +75 −0
  • .gitlab/issue_templates/support_request.md +64 −0
  • .gitlab/issue_templates/task.md +72 −0
  • .gitlab/merge_request_templates/Default.md +58 −0
  • README.md +4 −0
  • ai_translate.module +9 −37
  • ai_translate.post_update.php +24 −0
  • ai_translate.routing.yml +2 −1 fix

Full diff, 1.3.1 to 1.3.2 · Full diff, 1.4.0 to 1.4.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.