Drupal security updates, in plain English · Module

Anti-Spam by CleanTalk

6,783 sites report using it · on drupal.org · 2 security updates explained here

This module protects website forms from automated spam messages without using puzzles.

Below is every security update for Anti-Spam by CleanTalk 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.

Anti-Spam by CleanTalk

Moderately critical · 6,783 sites report using it · SA-CONTRIB-2026-042 · on drupal.org · Week of 3 June 2026

An administrator could place malicious code on the page if they can alter the response from the spam protection service. They could use this to view private information or change content on the website. They could not take full control of the website.

  • Who could do thisOnly someone with an administrator login.
  • Does it apply to youThis applies if someone can alter the response from the spam protection service through a compromised server or a man in the middle attack.
  • 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 Anti-Spam by CleanTalk to 9.7.1.

For developers: what the fix changed

The fix sanitises the API response message by passing it through `_cleantalk_filter_response()` in `_cleantalk_die()` and `ct_die()` within `src/CleantalkFuncs.php`, which now uses a custom HTML sanitisation method `apbct_sanitize_custom_message()`.

Also in this release Updated the bot detector wrapper URL and added a new DTO class in the common library.

9.7.0 to 9.7.1 5 commits, 4 files.

  • cleantalk.libraries.yml +1 −1
  • lib/Cleantalk/Common/Templates/Dto.php +59 −0
  • src/CleantalkFuncs.php +78 −2 fix
  • src/EventSubscriber/RequestSubscriber.php +2 −3 fix

Full diff, 9.7.0 to 9.7.1

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

Anti-Spam by CleanTalk

Moderately critical · 6,783 sites report using it · SA-CONTRIB-2026-014 · on drupal.org · Week of 25 February 2026

The module does not properly clean user input. Someone could use this to reveal protected information or manipulate website content.

  • Who could do thisAnyone visiting the site. No login needed.
  • Does it apply to youA site is affected if a visitor is challenged or blocked by the firewall.
  • 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 Anti-Spam by CleanTalk to 9.7.0.

For developers: what the fix changed

The fix sanitises the `$request_uri` variable using `htmlspecialchars` in `lib/Cleantalk/Common/Firewall/Modules/Sfw.php` to prevent reflected XSS when users are challenged by the firewall.

Also in this release The release also includes fixes for duplicated cookie settings, PostgreSQL database support improvements, and various code formatting updates.

9.6.1 to 9.7.0 35 commits, 43 files including 1 test.

  • .gitlab-ci.yml +2 −1
  • cleantalk.module +19 −5
  • composer.json +2 −2
  • js/apbct-public.js +7 −1
  • lib/Cleantalk/Common/Antispam/Cleantalk.php +13 −0
  • lib/Cleantalk/Common/Db/Db.php +138 −138
  • lib/Cleantalk/Common/Db/DbTablesCreator.php +7 −7
  • lib/Cleantalk/Common/Firewall/FirewallUpdater.php +132 −21
  • lib/Cleantalk/Common/Firewall/Modules/AntiCrawler.php +16 −4
  • lib/Cleantalk/Common/Firewall/Modules/Sfw.php +6 −4 fix
  • lib/Cleantalk/Common/Helper/Helper.php +2 −2
  • lib/Cleantalk/Common/Http/Request.php +4 −8

Full diff, 9.6.1 to 9.7.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.