Drupal security updates, in plain English · Module

Advanced Content Feedback (aka admin_feedback)

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

This module allows website visitors to leave feedback on pages and optionally attach a comment to their vote.

Below is every security update for Advanced Content Feedback (aka admin_feedback) 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.

Advanced Content Feedback (aka admin_feedback)

Moderately critical · 337 sites report using it · 2 security fixes · Week of 24 June 2026

2 security fixes in one update. Advanced Content Feedback (aka admin_feedback) fixed 2 separate security bugs this week: 1 access bypass / insecure direct object reference (idor), 1 cross site scripting. One update covers all of them. The most serious, SA-CONTRIB-2026-052, is explained here and the full list is at the end of the card.

An ordinary account on the site could bypass access checks when submitting a comment to alter another feedback record. They could modify other visitor feedback submissions on the website but they could not view any hidden information.

  • Who could do thisOnly someone with a login on your site.
  • Does it apply to youA site is affected if an attacker has a role with the access right to give feedback.
  • 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 Advanced Content Feedback (aka admin_feedback) to 8.x-2.8.

For developers: what the fix changed

This release carries 2 security fixes. The summary below is for SA-CONTRIB-2026-052, the most serious of them.

The fix replaces the base64-encoded feedback ID with an HMAC-signed token in `AdminFeedbackController::insertFeedback()` and verifies this signature in `AdminFeedbackController::updateFeedback()` to prevent users from modifying arbitrary feedback records. It also updates `AdminFeedbackAjaxForm` to handle the validation result and ensures that a comment can only be set once per feedback record.

Also in this release Added flood control for vote submissions, batch processing for CSV exports, a feature to delete all feedback for a specific node, and made JavaScript markup themeable.

8.x-2.7 to 8.x-2.8 30 commits, 19 files including 1 test.

  • README.md +55 −0
  • admin_feedback.install +25 −0
  • admin_feedback.libraries.yml +1 −1
  • admin_feedback.module +1 −0
  • admin_feedback.permissions.yml +4 −0
  • admin_feedback.routing.yml +17 −0
  • config/install/admin_feedback.settings.yml +7 −3
  • config/schema/admin_feedback.schema.yml +14 −0
  • css/admin_feedback.css +1 −1
  • js/admin_feedback.js +152 −98
  • logo.png +0 −0
  • src/Controller/AdminFeedbackController.php +277 −63 fix

Full diff, 8.x-2.7 to 8.x-2.8

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

All 2 security bugs this update fixes, worst first. Each link is the drupal.org notice for that one.

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.