Drupal security updates, in plain English · Module

Formatter Field

419 sites report using it · on drupal.org · 1 security update explained here

This module provides a way to choose how specific fields are displayed on individual pieces of content.

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

Formatter Field

Critical · 419 sites report using it · SA-CONTRIB-2026-048 · on drupal.org · Week of 17 June 2026

An ordinary account on the site could write malicious data directly into a display settings field. This could allow them to view or alter any information on the site including the underlying code.

  • Who could do thisOnly someone with a login on your site.
  • Does it apply to youA site is affected if a person has access rights to edit a piece of content with a display settings field and the site allows full edit access through a data feed or another direct method.
  • 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 Formatter Field to 2.0.0.

For developers: what the fix changed

The fix updates calls to `unserialize()` in `DefaultFormatter.php`, `FromFieldFormatter.php`, and `FormatterWidget.php` to include `['allowed_classes' => FALSE]`, preventing object injection. It also changes `#markup` to `#plain_text` when rendering settings in `DefaultFormatter.php`.

Also in this release Added compatibility for Drupal 9, 10, and 11, introduced GitLab CI configuration, fixed coding standards, and modernised the README file.

8.x-1.1 to 2.0.0 9 commits, 11 files.

  • .cspell-project-words.txt +5 −0
  • .gitlab-ci.yml +104 −0
  • README.md +44 −0
  • config/schema/formatter_field.schema.yml +2 −2
  • formatter_field.info.yml +1 −1
  • formatter_field.module +1 −1
  • readme.txt +0 −24
  • src/Plugin/Field/FieldFormatter/DefaultFormatter.php +5 −5 fix
  • src/Plugin/Field/FieldFormatter/FromFieldFormatter.php +3 −3 fix
  • src/Plugin/Field/FieldType/FormatterItem.php +9 −6
  • src/Plugin/Field/FieldWidget/FormatterWidget.php +8 −7 fix

Full diff, 8.x-1.1 to 2.0.0

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.