Drupal security updates, in plain English · Module

Quick Edit

36,982 sites report using it · on drupal.org · 1 security update explained here

This module allows people to edit content directly on the page they are viewing.

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

Quick Edit

Moderately critical · 36,982 sites report using it · SA-CONTRIB-2026-009 · on drupal.org · Week of 11 February 2026

The module does not properly clean up details about images when someone edits a page. A person with a standard account could use this to view private information. They could also change existing details or add new information to the site.

  • Who could do thisOnly someone with a login on your site.
  • Does it apply to youThis applies if a user has the access right to create or edit an affected piece of content.
  • 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 Quick Edit to 2.0.1 or 1.0.5, whichever branch you are on.

For developers: what the fix changed

The fix wraps the `settings.alt` and `settings.title` values with `Drupal.checkPlain()` in the image editing dialog templates within `js/theme.es6.js`, `js/theme.image.es6.js`, and their compiled counterparts. This ensures the values are properly sanitised to prevent cross-site scripting.

Also in this release The release also updated the GitLab CI configuration to remove a spellcheck ignore paths variable.

2.0.0 to 2.0.1 2 commits, 5 files.

  • .gitlab-ci.yml +0 −1
  • js/theme.es6.js +6 −6 fix
  • js/theme.image.es6.js +4 −4 fix
  • js/theme.image.js +3 −3 fix
  • js/theme.js +3 −3 fix

Full diff, 2.0.0 to 2.0.1 · Full diff, 1.0.4 to 1.0.5

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.