Drupal security updates, in plain English · Module

Internationalization Single Sign-On

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

This module automatically connects a user across different language domains if they are logged into the main language website.

Below is every security update for Internationalization Single Sign-On 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.

Internationalization Single Sign-On

Critical · 50 sites report using it · SA-CONTRIB-2026-081 · on drupal.org · Week of 22 July 2026

Anyone without logging in could bypass access controls and log in as another user. They could then view private information and make changes to the website as that person.

  • Who could do thisAnyone visiting the site. No login needed.
  • Does it apply to youThis applies if an attacker appears to come from the same internet address as the victim.
  • Has it been used in attacksNo sign of it.
  • How urgentDrupal rates this critical. Cyber Essentials expects a fix within 14 days. Do it this week.

Tell your developerUpdate Internationalization Single Sign-On to 8.x-1.8.

For developers: what the fix changed

The fix updates token generation in src/Service/Token.php to use cryptographically secure random bytes instead of a predictable hash and changes database queries to use exact matches for tokens and escape user IPs in LIKE conditions.

Also in this release Minor docblock updates and query cleanups.

8.x-1.7 to 8.x-1.8 1 commit, 2 files.

  • src/Controller/TokenController.php +1 −1
  • src/Service/Token.php +11 −11 fix

Full diff, 8.x-1.7 to 8.x-1.8

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.