Drupal security updates, in plain English · Module

Unpublished Node Permissions

4,321 sites report using it · on drupal.org · 2 security updates explained here

This module creates access rights per content type to control who can see unpublished pieces of content.

Below is every security update for Unpublished Node Permissions 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.

Unpublished Node Permissions

Critical · 4,321 sites report using it · SA-CONTRIB-2026-132 · on drupal.org · Week of 2 September 2026

The module allows people to see published pieces of content even if other access rules should hide them. A visitor could read published content that should be hidden. They could not change any data.

  • Who could do thisAnyone visiting the site. No login needed.
  • Does it apply to youAny site using this module.
  • 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 Unpublished Node Permissions to 8.x-1.8.

For developers: what the fix changed

The fix removes the code in unpublished_node_permissions_node_access_records within unpublished_node_permissions.module that incorrectly granted view access to published content. It also adds an update hook in unpublished_node_permissions.install to rebuild node access.

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

  • unpublished_node_permissions.install +7 −0 fix
  • unpublished_node_permissions.module +0 −10 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.

Unpublished Node Permissions

Critical · 4,321 sites report using it · SA-CONTRIB-2026-029 · on drupal.org · Week of 11 March 2026

A visitor without an account could see translated pieces of content that are not yet published. They could read the text of these translations. They could not change or delete the content.

  • Who could do thisAnyone visiting the site. No login needed.
  • Does it apply to youAny site using this module.
  • 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 Unpublished Node Permissions to 8.x-1.7.

For developers: what the fix changed

The fix updates unpublished_node_permissions_node_access_records in unpublished_node_permissions.module to iterate over all translation languages of a node and apply the unpublished node access grants per translation, including the language code in the grant. It also adds an update hook in unpublished_node_permissions.install to rebuild node access grants.

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

  • unpublished_node_permissions.install +7 −0 fix
  • unpublished_node_permissions.module +45 −24 fix

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

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.