Peter Brady, Drupal developer and private AI consultant

Drupal security updates, in plain English · Module

Webform REST

7,867 sites report using it · on drupal.org · 2 security updates explained here

This module lets other systems read and submit forms on your site over a data feed.

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

Webform REST

Less critical · 7,867 sites report using it · SA-CONTRIB-2026-186 · on drupal.org · Week of 23 September 2026

An ordinary account on the site could view form fields and submissions without the right access rights. They could read personal details submitted by other people. They could not edit or delete those submissions.

  • 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 Webform REST to 4.2.1.

For developers: what the fix changed

Adds access checks to `WebformCompleteSubmissionResource`, `WebformElementsResource`, and `WebformFieldsResource` to ensure the current user has permission to view the webform and its submissions.

Also in this release Fixed PHPCS warnings, updated GitLab CI configuration, corrected typos in error messages, and made REST GET endpoints cacheable by replacing ModifiedResourceResponse with ResourceResponse.

4.2.0 to 4.2.1 7 commits, 15 files including 4 tests.

  • .gitlab-ci.yml +20 −3
  • src/Event/WebformSubmitReturnEvent.php +13 −2
  • src/Form/WebformRestForm.php +8 −35
  • src/Plugin/rest/resource/WebformCompleteSubmissionResource.php +58 −13 fix
  • src/Plugin/rest/resource/WebformElementsResource.php +32 −6 fix
  • src/Plugin/rest/resource/WebformFieldsResource.php +24 −8 fix
  • src/Plugin/rest/resource/WebformSubmissionResource.php +22 −21
  • src/Plugin/rest/resource/WebformSubmitResource.php +21 −23
  • webform_rest.install +3 −2
  • webform_rest.permissions.yml +1 −1
  • webform_rest.routing.yml +1 −1

Full diff, 4.2.0 to 4.2.1

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

Webform REST

Moderately critical · 7,867 sites report using it · SA-CONTRIB-2026-087 · on drupal.org · Week of 22 July 2026

An ordinary account holder could view form submissions that they should not have access to. They could also add or alter form submissions without the correct access rights.

  • Who could do thisOnly someone with a login on your site.
  • Does it apply to youThis applies if an attacker already has access rights to use the 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 Webform REST to 4.1.0.

For developers: what the fix changed

The fix adds access checks for creating, viewing, updating, and deleting webform submissions in `WebformSubmissionResource.php` and `WebformSubmitResource.php`. It uses the `access()` method on the webform and webform submission entities to ensure the current user has the appropriate permissions.

Also in this release The release also added a new event for webform submission returns, token support to the field endpoint, a composer.json file, and fixed handlers and hooks being called twice.

4.0.3 to 4.1.0 7 commits, 5 files.

  • composer.json +38 −0
  • src/Event/WebformSubmitReturnEvent.php +79 −0
  • src/Plugin/rest/resource/WebformFieldsResource.php +21 −1
  • src/Plugin/rest/resource/WebformSubmissionResource.php +89 −0 fix
  • src/Plugin/rest/resource/WebformSubmitResource.php +69 −16 fix

Full diff, 4.0.3 to 4.1.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.

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