Drupal security updates, in plain English · Module

Salesforce Suite

3,942 sites report using it · on drupal.org · 1 security update explained here

This module connects the website to Salesforce to share information like users and contacts between the two systems.

Below is every security update for Salesforce Suite 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.

Salesforce Suite

Moderately critical · 3,942 sites report using it · SA-CONTRIB-2026-063 · on drupal.org · Week of 24 June 2026

An ordinary account on the site could hijack the authorisation token and connect the website to their own Salesforce account. They could view restricted synchronisation details and modify certain contact records. They could not access or alter every piece of information on the website.

  • Who could do thisOnly someone with a login on your site.
  • Does it apply to youA site is affected if it uses a version older than version six and has the Salesforce OAuth feature enabled with an active authorisation profile.
  • 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 Salesforce Suite to 5.1.3.

For developers: what the fix changed

The fix adds a `state` parameter to the OAuth authorization request in `SalesforceOAuthPlugin::submitConfigurationForm` and validates it during the callback in `SalesforceOAuthController::oauthCallback` to prevent CSRF attacks.

Also in this release The release also includes PHP 8.3 compatibility fixes, updates to the JWT authentication plugin, enhancements to mapping and pull/push events, and various bug fixes.

5.1.2 to 5.1.3 34 commits, 78 files including 8 tests.

  • .gitignore +3 −1
  • .gitlab-ci.yml +2 −1
  • composer.json +1 −1
  • css/salesforce.css +1 −1
  • modules/salesforce_example/src/EventSubscriber/SalesforceExampleSubscriber.php +3 −0
  • modules/salesforce_jwt/composer.json +1 −1
  • modules/salesforce_jwt/src/Consumer/JWTCredentials.php +41 −6
  • modules/salesforce_jwt/src/Plugin/SalesforceAuthProvider/SalesforceJWTGovCloudPlugin.php +4 −22
  • modules/salesforce_jwt/src/Plugin/SalesforceAuthProvider/SalesforceJWTPlugin.php +338 −29
  • modules/salesforce_logger/salesforce_logger.services.yml +2 −0
  • modules/salesforce_logger/src/Form/SettingsForm.php +6 −1
  • modules/salesforce_mapping/config/schema/salesforce_mapping.schema.yml +8 −0

Full diff, 5.1.2 to 5.1.3

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.