Peter Brady, Drupal developer and private AI consultant

Drupal security updates, in plain English · Module

Login Disable

499 sites report using it · on drupal.org · 2 security updates explained here

This module prevents users from logging in unless they know a secret key to add to the login page address.

Below is every security update for Login Disable 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.

Login Disable

Moderately critical · 499 sites report using it · SA-CONTRIB-2026-070 · on drupal.org · Week of 8 July 2026

The module does not stop attackers from repeatedly guessing the secret key. An ordinary account on the site could guess the key to bypass the login block. They could then read some restricted data and change or add some data.

  • Who could do thisOnly someone with a login on your site.
  • Does it apply to youThis applies if an attacker has a valid username and password.
  • 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 Login Disable to 2.1.4.

For developers: what the fix changed

In login_disable.module, the _login_disable_form_user_login_alter function was updated to integrate flood control, registering failed attempts and blocking access when the limit is reached.

Also in this release Added a GitLab CI test variable and updated the README file.

2.1.3 to 2.1.4 2 commits, 3 files.

  • .gitlab-ci.yml +2 −0
  • README.txt +6 −0
  • login_disable.module +30 −8 fix

Full diff, 2.1.3 to 2.1.4

The comparison is against the release immediately before the fix. If your site is on an older release, more will have changed.

Login Disable

Less critical · 499 sites report using it · SA-CONTRIB-2026-008 · on drupal.org · Week of 4 February 2026

A person with an ordinary account on the site can log in using a specific web address without needing the secret code. They cannot read any extra information. They cannot change anything on the site.

  • 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 less critical. Fix it with the next routine update.

Tell your developerUpdate Login Disable to 2.1.3.

For developers: what the fix changed

The fix adds a route subscriber in `src/EventSubscriber/LoginDisableRouteSubscriber.php` to attach a custom access check to the `user.login.http` route. The access check, implemented in `src/Access/LoginDisableAccessCheck.php`, verifies that the required access key is present in the request URL before allowing login.

Also in this release Added automated tests for the HTTP login functionality.

2.1.2 to 2.1.3 1 commit, 4 files including 1 test.

  • login_disable.services.yml +13 −0 fix
  • src/Access/LoginDisableAccessCheck.php +58 −0 fix
  • src/EventSubscriber/LoginDisableRouteSubscriber.php +23 −0 fix

Full diff, 2.1.2 to 2.1.3

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.

Peter Brady, Drupal developer and private AI consultant

PNB Technologies Limited
55 Yew Tree Road, Ormskirk
Lancashire, L39 1NT, United Kingdom

Company Reg: 07166600
VAT Reg: GB986726850

© 2026 Peter Brady. All rights reserved.

Connect on LinkedIn

Links

Reference