View online: https://www.drupal.org/sa-contrib-2026-027
Project: OpenID Connect / OAuth client [1]
Date: 2026-March-04
Security risk: *Less critical* 9 ∕ 25
AC:Complex/A:User/CI:Some/II:None/E:Theoretical/TD:Default [2]
Vulnerability: Access bypass
Affected versions: <1.5.0
CVE IDs: CVE-2026-3532
Description:
This module enables you to use an external OpenID Connect login provider to
authenticate and log in users on your site. If a user signs in with a login
provider for the first time on the website, a new Drupal user will be
created.
The module doesn't sufficiently validate the uniqueness of certain user
fields depending on the database engine and its collation.
As a result, a user may be able to register with the same email address as
another user.
This may lead to data integrity issues.
Solution:
Install the latest version:
* If you use the OpenID Connect 8.x-1.x module, upgrade to OpenID Connect
8.x-1.5 [3]
Updating OpenID Connect will not solve potential issues with existing
accounts affected by this bug. See Fixing emails that vary only by case [4]
for additional guidance.
Reported By:
* Eric Smith (ericgsmith) [5]
Fixed By:
* Philip Frilling (pfrilling) [6]
Coordinated By:
* Greg Knaddison (greggles) [7] of the Drupal Security Team
* Drew Webber (mcdruid) [8] of the Drupal Security Team
* Juraj Nemec (poker10) [9] of the Drupal Security Team
------------------------------------------------------------------------------
Contribution record [10]
[1] https://www.drupal.org/project/openid_connect
[2] https://www.drupal.org/security-team/risk-levels
[3] https://www.drupal.org/project/openid_connect/releases/8.x-1.5
[4] https://www.drupal.org/node/3486109
[5] https://www.drupal.org/u/ericgsmith
[6] https://www.drupal.org/u/pfrilling
[7] https://www.drupal.org/u/greggles
[8] https://www.drupal.org/u/mcdruid
[9] https://www.drupal.org/u/poker10
[10]
https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…
View online: https://www.drupal.org/sa-contrib-2026-025
Project: OpenID Connect / OAuth client [1]
Date: 2026-March-04
Security risk: *Moderately critical* 10 ∕ 25
AC:Basic/A:User/CI:Some/II:None/E:Theoretical/TD:Default [2]
Vulnerability: Server-side request forgery, Information disclosure
Affected versions: <1.5.0
CVE IDs: CVE-2026-3530
Description:
This module enables you to use an external OpenID Connect login provider to
authenticate and log in users on your site. If a user signs in with a login
provider for the first time on the website, a new Drupal user will be
created.
The module doesn't sufficiently validate certain fields coming from the
identity provider, which could lead to SSRF and information disclosures.
This vulnerability is mitigated by:
- an attacker must have access to the identity provider to provide
compromised data at the source profile.
- a site must have specific field mappings configured
Solution:
Install the latest version:
* If you use the OpenID Connect 8.x-1.x module upgrade to OpenID Connect
8.x-1.5 [3]
Reported By:
* Drew Webber (mcdruid) [4] of the Drupal Security Team
Fixed By:
* Drew Webber (mcdruid) [5] of the Drupal Security Team
* Philip Frilling (pfrilling) [6]
Coordinated By:
* Damien McKenna (damienmckenna) [7] of the Drupal Security Team
* Greg Knaddison (greggles) [8] of the Drupal Security Team
* Drew Webber (mcdruid) [9] of the Drupal Security Team
* Juraj Nemec (poker10) [10] of the Drupal Security Team
------------------------------------------------------------------------------
Contribution record [11]
[1] https://www.drupal.org/project/openid_connect
[2] https://www.drupal.org/security-team/risk-levels
[3] https://www.drupal.org/project/openid_connect/releases/8.x-1.5
[4] https://www.drupal.org/u/mcdruid
[5] https://www.drupal.org/u/mcdruid
[6] https://www.drupal.org/u/pfrilling
[7] https://www.drupal.org/u/damienmckenna
[8] https://www.drupal.org/u/greggles
[9] https://www.drupal.org/u/mcdruid
[10] https://www.drupal.org/u/poker10
[11]
https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…
View online: https://www.drupal.org/sa-contrib-2026-024
Project: Google Analytics GA4 [1]
Date: 2026-March-04
Security risk: *Moderately critical* 12 ∕ 25
AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:Default [2]
Vulnerability: Cross-site Scripting
Affected versions: <1.1.13
CVE IDs: CVE-2026-3529
Description:
The Google Analytics GA4 module enables users to add custom attributes to the
script tag used to load the Google Analytics library. The module does not
sufficiently sanitize these attributes.
This vulnerability is mitigated by the fact that an attacker must have a role
with the "ga4 configure" (or "administer google analytics ga4 settings")
permission.
An attacker with this permission could inject malicious JavaScript via event
handlers (such as onload) or override the script source, leading to a
Cross-Site Scripting (XSS) attack on all pages where the GA4 script is
loaded.
Solution:
Install the latest version:
* If you use the Google Analytics GA4 module, upgrade to Google Analytics
GA4 1.1.13 [3]
Reported By:
* Pierre Rudloff (prudloff) [4] provisional member of the Drupal Security
Team
Fixed By:
* Sujan Shrestha (sujan shrestha) [5]
Coordinated By:
* Greg Knaddison (greggles) [6] of the Drupal Security Team
* Juraj Nemec (poker10) [7] of the Drupal Security Team
------------------------------------------------------------------------------
Contribution record [8]
[1] https://www.drupal.org/project/ga4_google_analytics
[2] https://www.drupal.org/security-team/risk-levels
[3] https://www.drupal.org/project/ga4_google_analytics/releases/1.1.13
[4] https://www.drupal.org/u/prudloff
[5] https://www.drupal.org/u/sujan-shrestha
[6] https://www.drupal.org/u/greggles
[7] https://www.drupal.org/u/poker10
[8]
https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…
View online: https://www.drupal.org/sa-contrib-2026-022
Project: AJAX Dashboard [1]
Date: 2026-March-04
Security risk: *Critical* 17 ∕ 25
AC:None/A:None/CI:Some/II:Some/E:Theoretical/TD:Default [2]
Vulnerability: Access bypass
Affected versions: <3.1.0
CVE IDs: CVE-2026-3527
Description:
AJAX Dashboard: Entity Dashboards enables you to create configurable
dashboards attached to entities which include AJAX-reloading of a main
content area based on inputs from a configurable set of buttons.
The module doesn't sufficiently check access on the dashboard configuration
route. Unauthorized users could access the entity dashboard configuration
page and either enable or disable dashboards. The affected administration
page does not permit editing the configurations of the dashboards themselves.
The vulnerability is mitigated by the fact that the AJAX Dashboard Entity
Dashboard submodule must be enabled.
Solution:
Install the latest version of the AJAX Dashboard module, which includes the
update to AJAX Dashboard: Entity Dashboards:
* If you use the AJAX Dashboard module, upgrade to AJAX Dashboard 3.1.0 [3]
Reported By:
* Juraj Nemec (poker10) [4] of the Drupal Security Team
Fixed By:
* Michael Nolan (laboratory.mike) [5]
Coordinated By:
* Bram Driesen (bramdriesen) [6] provisional member of the Drupal Security
Team
* Greg Knaddison (greggles) [7] of the Drupal Security Team
* Juraj Nemec (poker10) [8] of the Drupal Security Team
------------------------------------------------------------------------------
Contribution record [9]
[1] https://www.drupal.org/project/ajax_dashboard
[2] https://www.drupal.org/security-team/risk-levels
[3] https://www.drupal.org/node/3576913
[4] https://www.drupal.org/u/poker10
[5] https://www.drupal.org/u/laboratorymike
[6] https://www.drupal.org/u/bramdriesen
[7] https://www.drupal.org/u/greggles
[8] https://www.drupal.org/u/poker10
[9]
https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…