Scheduler security updates, in plain English

Scheduler

125,356 sites report using it · on drupal.org · 1 security update explained here

This module allows editors to set specific dates and times for content to become public or be hidden.

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

Scheduler

Moderately critical · 125,356 sites report using it · SA-CONTRIB-2026-306 · on drupal.org · Week of 4 November 2026

The module does not properly check if a user is allowed to change scheduled dates. An ordinary account on the site could make content public too early or hide it at the wrong time. They might uncover hidden details or alter content schedules.

Who could do thisOnly someone with a login on your site.
Does it apply to youSites are affected if an attacker has the access right to edit the content and the content can be edited through a web services data feed.
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 Scheduler to 8.x-1.7, 2.2.3 or 2.3.1, whichever branch you are on.

For developers: what the fix changed

The fix implements `hook_entity_field_access()` in `scheduler.module` to restrict edit access to the `publish_on` and `unpublish_on` fields, ensuring that users must have the 'schedule publishing of nodes' permission and that the content type has scheduling enabled.

Also in this release The release also includes CI pipeline updates, deprecation fixes for Drupal 11.3, and test coverage improvements.

8.x-1.6 to 8.x-1.7 8 commits, 19 files including 6 tests.

.gitlab-ci.yml +24 −35
composer.json +1 −0
phpcs.xml +0 −5
phpstan-baseline-to-fix.neon +1 −1
phpstan-baseline.neon +14 −1
phpstan.neon +1 −1
scheduler.module +37 −1 fix
scheduler_rules_integration/composer.json +1 −0
scheduler_rules_integration/src/Plugin/RulesAction/RemovePublishingDate.php +1 −1
scheduler_rules_integration/src/Plugin/RulesAction/RemoveUnpublishingDate.php +1 −1
scheduler_rules_integration/src/Plugin/RulesAction/SetPublishingDate.php +1 −1
scheduler_rules_integration/src/Plugin/RulesAction/SetUnpublishingDate.php +1 −1

Full diff, 8.x-1.6 to 8.x-1.7 · Full diff, 2.2.2 to 2.2.3 · Full diff, 2.3.0 to 2.3.1

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

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.

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.

Scheduler

Scheduler

Send me your Drupal site's address.

Get in touch

Links

Reference