Drupal security updates, in plain English · Module

OAuth2 Token Manager

on drupal.org · 1 security update explained here

This module manages system wide access tokens for connecting the website to external services.

Below is every security update for OAuth2 Token Manager 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.

OAuth2 Token Manager

Critical · no install count published · SA-CONTRIB-2026-290 · on drupal.org · Week of 28 October 2026

The module does not restrict access to its connection pages. A visitor could connect the site to an account they control and change or add data. They could not do this without finding a specific code from a previous connection attempt in the server logs.

  • Who could do thisAnyone visiting the site. No login needed.
  • Does it apply to youAn attacker can find the state value from a previous system token setup in the server logs.
  • 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 OAuth2 Token Manager to 8.x-1.2.

For developers: what the fix changed

The fix restricts access to the OAuth2 validation routes by replacing `_access: 'TRUE'` with specific administer permissions in the routing files for Box, Quip, and Slack. It also updates `ValidationControllerBase::validate` to clear the initialisation state after use and ensures it is not empty before comparing it to the request state.

Also in this release The release also fixed a lock contention bug in `refreshSystemAccessToken()` and added automated tests.

8.x-1.1 to 8.x-1.2 2 commits, 13 files including 2 tests.

  • modules/box/box_token_manager.install +15 −0 fix
  • modules/box/box_token_manager.permissions.yml +4 −0 fix
  • modules/box/box_token_manager.routing.yml +1 −1 fix
  • modules/quip/quip_token_manager.install +15 −0 fix
  • modules/quip/quip_token_manager.permissions.yml +4 −0 fix
  • modules/quip/quip_token_manager.routing.yml +1 −1 fix
  • modules/slack/slack_token_manager.install +15 −0 fix
  • modules/slack/slack_token_manager.permissions.yml +4 −0 fix
  • modules/slack/slack_token_manager.routing.yml +1 −1 fix
  • src/Controller/ValidationControllerBase.php +4 −3 fix
  • src/TokenManager.php +10 −3 fix

Full diff, 8.x-1.1 to 8.x-1.2

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.