Security-news

security-news@drupal.org

1 participants
1782 discussions

Microsoft Entra ID SSO Login - Critical - Access bypass - SA-CONTRIB-2026-005
by security-news＠drupal.org 14 Jan '26

14 Jan '26

View online: https://www.drupal.org/sa-contrib-2026-005 Project: Microsoft Entra ID SSO Login [1] Date: 2026-January-14 Security risk: *Critical* 16 ∕ 25 AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:All [2] Vulnerability: Access bypass Affected versions: <1.0.4 CVE IDs: CVE-2026-0948 Description: This module enables Drupal sites to authenticate users via Microsoft Entra ID (formerly Azure AD) using OAuth 2.0. The module doesn't sufficiently validate API responses from Microsoft allowing complete account takeover of any user, including site administrators, without requiring any credentials or access to the target's email account. Solution: 1) If you use the Microsoft Entra ID SSO Login, update to the module's latest version Microsoft Entra ID SSO Login 2.0.0 [3] (or Microsoft Entra ID SSO Login 1.0.4 [4]). 2) Review the release node and module documentation for information on how to update your configuration with the new module release. 3) Site administrators should also review their security settings after upgrading and consider enabling the "Block User 1" and "Block Administrator role" options for additional protection. Reported By: * Ashish Verma (ashish.verma85) [5] * Dheeraj Jhamtani (dheeraj jhamtani) [6] * Marcelo Vani (marcelovani) [7] Fixed By: * Jaseer Kinangattil (jaseerkinangattil) [8] Coordinated By: * Greg Knaddison (greggles) [9] of the Drupal Security Team * Juraj Nemec (poker10) [10] of the Drupal Security Team ------------------------------------------------------------------------------ Contribution record [11] [1] https://www.drupal.org/project/social_auth_entra_id [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/social_auth_entra_id/releases/2.0.0 [4] https://www.drupal.org/project/social_auth_entra_id/releases/1.0.4 [5] https://www.drupal.org/u/ashishverma85 [6] https://www.drupal.org/u/dheeraj-jhamtani [7] https://www.drupal.org/u/marcelovani [8] https://www.drupal.org/u/jaseerkinangattil [9] https://www.drupal.org/u/greggles [10] https://www.drupal.org/u/poker10 [11] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

AT Internet Piano Analytics - Moderately critical - Cross-site Scripting - SA-CONTRIB-2026-004
by security-news＠drupal.org 14 Jan '26

14 Jan '26

View online: https://www.drupal.org/sa-contrib-2026-004 Project: AT Internet Piano Analytics [1] Date: 2026-January-14 Security risk: *Moderately critical* 13 ∕ 25 AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2] Vulnerability: Cross-site Scripting Affected versions: <1.0.1 || >=2.0.0 <2.3.1 CVE IDs: CVE-2026-0947 Description: This module integrates the AT Internet Piano Analytics service. The module does not filter administrator-entered text leading to a persistent Cross-site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer pianoanalytics". Solution: Install the latest version and confirm the permissions associated with the module are assigned to appropriate roles. * If you use the AT Internet Piano Analytics module for Drupal 10+, upgrade to AT Internet Piano Analytics 2.3.1 [3] * If you use the AT Internet Piano Analytics module for Drupal 9, upgrade to AT Internet Piano Analytics 1.0.1 [4] Reported By: * Pierre Rudloff (prudloff) [5] provisional member of the Drupal Security Team Fixed By: * Frank Mably (mably) [6] Coordinated By: * Greg Knaddison (greggles) [7] of the Drupal Security Team * Juraj Nemec (poker10) [8] of the Drupal Security Team * Pierre Rudloff (prudloff) [9] provisional member of the Drupal Security Team ------------------------------------------------------------------------------ Contribution record [10] [1] https://www.drupal.org/project/pianoanalytics [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/pianoanalytics/releases/2.3.1 [4] https://www.drupal.org/project/pianoanalytics/releases/1.0.1 [5] https://www.drupal.org/u/prudloff [6] https://www.drupal.org/u/mably [7] https://www.drupal.org/u/greggles [8] https://www.drupal.org/u/poker10 [9] https://www.drupal.org/u/prudloff [10] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

AT Internet SmartTag - Moderately critical - Cross-site Scripting - SA-CONTRIB-2026-003
by security-news＠drupal.org 14 Jan '26

14 Jan '26

View online: https://www.drupal.org/sa-contrib-2026-003 Project: AT Internet SmartTag [1] Date: 2026-January-14 Security risk: *Moderately critical* 13 ∕ 25 AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2] Vulnerability: Cross-site Scripting Affected versions: <1.0.1 CVE IDs: CVE-2026-0946 Description: This module integrates the AT Internet SmartTag service. The module does not filter administrator-entered text leading to a persistent Cross-site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer atsmarttag". Solution: Install the latest version and confirm the permissions associated with the module are assigned to appropriate roles. * If you use the AT Internet SmartTag module for Drupal 9 and 10, upgrade to AT Internet SmartTag 1.0.1 [3] Reported By: * Pierre Rudloff (prudloff) [4] provisional member of the Drupal Security Team Fixed By: * Frank Mably (mably) [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/atsmarttag [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/atsmarttag/releases/1.0.1 [4] https://www.drupal.org/u/prudloff [5] https://www.drupal.org/u/mably [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…

1 0

Role Delegation - Moderately critical - Access bypass - SA-CONTRIB-2026-002
by security-news＠drupal.org 14 Jan '26

14 Jan '26

View online: https://www.drupal.org/sa-contrib-2026-002 Project: Role Delegation [1] Date: 2026-January-14 Security risk: *Moderately critical* 13 ∕ 25 AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:Default [2] Vulnerability: Access bypass Affected versions: >=1.3.0 <1.5.0 CVE IDs: CVE-2026-0945 Description: This module allows site administrators to grant specific roles the authority to assign selected roles to users, without them needing the "administer permissions" permission. The module contains an access bypass vulnerability when used in combination with the Views Bulk Operations module. A user with the ability to delegate a role is also able to assign the administrator role, including to their own user. This vulnerability is mitigated by the fact that an attacker must have access to a view of users with the Views Bulk Operations module enabled. Solution: Install the latest version: * If you use the Role Delegation module for Drupal ^10.3 || ^11, upgrade to Role Delegation 8.x-1.5 [3] Reported By: * Drew Webber (mcdruid) [4] of the Drupal Security Team Fixed By: * Adam Bramley (acbramley) [5] * Dieter Holvoet (dieterholvoet) [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/role_delegation [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/role_delegation/releases/8.x-1.5 [4] https://www.drupal.org/u/mcdruid [5] https://www.drupal.org/u/acbramley [6] https://www.drupal.org/u/dieterholvoet [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…

1 0

Group invite - Moderately critical - Access bypass - SA-CONTRIB-2026-001
by security-news＠drupal.org 14 Jan '26

14 Jan '26

View online: https://www.drupal.org/sa-contrib-2026-001 Project: Group invite [1] Date: 2026-January-14 Security risk: *Moderately critical* 14 ∕ 25 AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] Vulnerability: Access bypass Affected versions: <2.3.9 || >=3.0.0 <3.0.4 || >=4.0.0 <4.0.4 CVE IDs: CVE-2026-0944 Description: This module enables allows group managers to invite people into their group. The module doesn't sufficiently check access under certain circumstances, allowing unauthorized users to access the group's content. This vulnerability is mitigated by the fact that it only occurs when certain uncommon actions are taken by a user with the permission to create group invites. Solution: Install the latest version: * If you use the Group Invite module 2.3.x, upgrade to Group Invite 2.3.9 [3] * If you use the Group Invite module 3.0.x, upgrade to Group Invite 3.0.4 [4] * If you use the Group Invite module 4.0.x, upgrade to Group Invite 4.0.4 [5] Reported By: * Kevin Quillen (kevinquillen) [6] Fixed By: * eduardo morales alberti [7] * Kevin Quillen (kevinquillen) [8] * Nikolay Lobachev (lobsterr) [9] * Ricardo Sanz Ante (tunic) [10] Coordinated By: * Greg Knaddison (greggles) [11] of the Drupal Security Team * Juraj Nemec (poker10) [12] of the Drupal Security Team ------------------------------------------------------------------------------ Contribution record [13] [1] https://www.drupal.org/project/ginvite [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/ginvite/releases/2.3.9 [4] https://www.drupal.org/project/ginvite/releases/3.0.4 [5] https://www.drupal.org/project/ginvite/releases/4.0.4 [6] https://www.drupal.org/u/kevinquillen [7] https://www.drupal.org/u/eduardo-morales-alberti [8] https://www.drupal.org/u/kevinquillen [9] https://www.drupal.org/u/lobsterr [10] https://www.drupal.org/u/tunic [11] https://www.drupal.org/u/greggles [12] https://www.drupal.org/u/poker10 [13] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

HTTP Client Manager - Less critical - Information disclosure - SA-CONTRIB-2025-126
by security-news＠drupal.org 17 Dec '25

17 Dec '25

View online: https://www.drupal.org/sa-contrib-2025-126 Project: HTTP Client Manager [1] Date: 2025-December-17 Security risk: *Less critical* 8 ∕ 25 AC:Complex/A:User/CI:Some/II:None/E:Theoretical/TD:Uncommon [2] Vulnerability: Information disclosure Affected versions: <9.3.13 || >=10.0.0 <10.0.2 || >=11.0.0 <11.0.1 CVE IDs: CVE-2025-14840 Description: Http Client Manager introduces a new Guzzle based plugin which allows you to manage HTTP clients using Guzzle Service Descriptions via YAML, JSON or PHP files, in a simple and efficient way. The modules allows administrators to configure HTTP requests as part of Event Condition Action (ECA) automation. The module does not sufficiently maintain separation of data from request operations, potentially leading to information disclosure in very uncommon situations. Solution: Install the latest version: * If you use the Http Client Manager module 9.3.x, upgrade to Http Client Manager 9.3.13 [3] * If you use the Http Client Manager module 10.0.x, upgrade to Http Client Manager 10.0.2 [4] * If you use the Http Client Manager module 11.0.x, upgrade to Http Client Manager 11.0.1 [5] Reported By: * mxh [6] Fixed By: * Adriano Cori (aronne) [7] * mxh [8] Coordinated By: * Greg Knaddison (greggles) [9] of the Drupal Security Team * Juraj Nemec (poker10) [10] of the Drupal Security Team ------------------------------------------------------------------------------ Contribution record [11] [1] https://www.drupal.org/project/http_client_manager [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/http_client_manager/releases/9.3.13 [4] https://www.drupal.org/project/http_client_manager/releases/10.0.2 [5] https://www.drupal.org/project/http_client_manager/releases/11.0.1 [6] https://www.drupal.org/u/mxh [7] https://www.drupal.org/u/aronne [8] https://www.drupal.org/u/mxh [9] https://www.drupal.org/u/greggles [10] https://www.drupal.org/u/poker10 [11] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Acquia Content Hub - Moderately critical - Cross-Site Request Forgery - SA-CONTRIB-2025-125
by security-news＠drupal.org 10 Dec '25

10 Dec '25

View online: https://www.drupal.org/sa-contrib-2025-125 Project: Acquia Content Hub [1] Date: 2025-December-10 Security risk: *Moderately critical* 11 ∕ 25 AC:Complex/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] Vulnerability: Cross-Site Request Forgery Affected versions: <3.6.4 || >=3.7.0 <3.7.3 || >=3.8.0 <3.8.0 CVE IDs: CVE-2025-14472 Description: This module provides a centralized content distribution and syndication solution so thta customers can publish, reuse, and syndicate content across a network of Drupal websites. The module doesn't sufficiently protect export routes from cross-site request forgery (CSRF) attacks, potentially allowing an attacker to trick an admin into exporting an unwanted entity. Solution: Install the latest version: * If you use Acquia Content Hub 3.6.x, upgrade to Acquia Content Hub 3.6.4 [3]. * If you use Acquia Content Hub 3.7.x, upgrade to Acquia Content Hub 3.7.3 [4]. * The latest version, Acquia Content Hub 3.8.0 [5], is also now available with both the security fix and other improvements. Reported By: * Lee Rowlands (larowlan) [6] of the Drupal Security Team Fixed By: * Kirti Garg (kirti_garg) [7] * Narendra Shenvi Desai (n4r3n) [8] * Peter Pajor (pajor) [9] Coordinated By: * Greg Knaddison (greggles) [10] of the Drupal Security Team * Juraj Nemec (poker10) [11] of the Drupal Security Team * Jess (xjm) [12] of the Drupal Security Team ------------------------------------------------------------------------------ Contribution record [13] [1] https://www.drupal.org/project/acquia_contenthub [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/acquia_contenthub/releases/3.6.4 [4] https://www.drupal.org/project/acquia_contenthub/releases/3.7.3 [5] https://www.drupal.org/project/acquia_contenthub/releases/3.8.0 [6] https://www.drupal.org/u/larowlan [7] https://www.drupal.org/u/kirti_garg [8] https://www.drupal.org/u/n4r3n [9] https://www.drupal.org/u/pajor [10] https://www.drupal.org/u/greggles [11] https://www.drupal.org/u/poker10 [12] https://www.drupal.org/u/xjm [13] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Disable Login Page - Critical - Access bypass - SA-CONTRIB-2025-124
by security-news＠drupal.org 03 Dec '25

03 Dec '25

View online: https://www.drupal.org/sa-contrib-2025-124 Project: Disable Login Page [1] Date: 2025-December-03 Security risk: *Critical* 15 ∕ 25 AC:Complex/A:None/CI:Some/II:Some/E:Theoretical/TD:All [2] Vulnerability: Access bypass Affected versions: <1.1.3 CVE IDs: CVE-2025-13986 Description: This module enables you to disable the standard Drupal login form (/user/login) so site owners can prevent interactive logins via the UI. The module does not sufficiently block authentication when the REST/HTTP login route is used. An attacker (or legitimate user) with valid credentials can authenticate using the REST login endpoint (/user/login?_format=json) or other HTTP-based authentication routes, effectively bypassing the module’s protection of the UI login page. This vulnerability is mitigated by the fact that an attacker must already possess valid account credentials. Solution: Install the latest version: * If you use the Disable Login Page module, upgrade to Disable Login Page 1.1.3 [3] Reported By: * Pierre Rudloff (prudloff) [4] provisional member of the Drupal Security Team Fixed By: * Anoop John (anoopjohn) [5] * Jijo Joseph (jijojoseph_zyxware) [6] * Pierre Rudloff (prudloff) [7] provisional member of the Drupal Security Team Coordinated By: * cilefen (cilefen) [8] of the Drupal Security Team * Greg Knaddison (greggles) [9] of the Drupal Security Team * Drew Webber (mcdruid) [10] of the Drupal Security Team * Juraj Nemec (poker10) [11] of the Drupal Security Team * Jess (xjm) [12] of the Drupal Security Team ------------------------------------------------------------------------------ Contribution record [13] [1] https://www.drupal.org/project/disable_login [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/disable_login/releases/1.1.3 [4] https://www.drupal.org/u/prudloff [5] https://www.drupal.org/u/anoopjohn [6] https://www.drupal.org/u/jijojoseph_zyxware [7] https://www.drupal.org/u/prudloff [8] https://www.drupal.org/u/cilefen [9] https://www.drupal.org/u/greggles [10] https://www.drupal.org/u/mcdruid [11] https://www.drupal.org/u/poker10 [12] https://www.drupal.org/u/xjm [13] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Entity Share - Moderately critical - Access bypass, Information Disclosure - SA-CONTRIB-2025-123
by security-news＠drupal.org 03 Dec '25

03 Dec '25

View online: https://www.drupal.org/sa-contrib-2025-123 Project: Entity Share [1] Date: 2025-December-03 Security risk: *Moderately critical* 14 ∕ 25 AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] Vulnerability: Access bypass, Information Disclosure Affected versions: <3.13.0 CVE IDs: CVE-2025-13985 Description: This module enables you to deploy content from one Drupal website to another. The module provides some default configuration without sufficient access control. This vulnerability is mitigated by the fact that an administrator can add some default access control permission. Solution: Install the latest version: * If you use the Entity Share module for Drupal on branch 8.x-3.x, upgrade to Entity Share 8.x-3.13 [3]. For a hotfix without upgrading the module, edit the entity_share_client_entity_import_status view to ensure access permissions are set. Reported By: * Jürgen Haas (jurgenhaas) [4] Fixed By: * Florent Torregrosa (grimreaper) [5] * Joachim Noreiko (joachim) [6] Coordinated By: * Bram Driesen (bramdriesen) [7] provisional member of the Drupal Security Team * cilefen (cilefen) [8] of the Drupal Security Team * Greg Knaddison (greggles) [9] of the Drupal Security Team * Drew Webber (mcdruid) [10] of the Drupal Security Team * Juraj Nemec (poker10) [11] of the Drupal Security Team * Jess (xjm) [12] of the Drupal Security Team ------------------------------------------------------------------------------ Contribution record [13] [1] https://www.drupal.org/project/entity_share [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/node/3561230 [4] https://www.drupal.org/u/jurgenhaas [5] https://www.drupal.org/u/grimreaper [6] https://www.drupal.org/u/joachim [7] https://www.drupal.org/u/bramdriesen [8] https://www.drupal.org/u/cilefen [9] https://www.drupal.org/u/greggles [10] https://www.drupal.org/u/mcdruid [11] https://www.drupal.org/u/poker10 [12] https://www.drupal.org/u/xjm [13] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Next.js - Critical - Access bypass - SA-CONTRIB-2025-122
by security-news＠drupal.org 03 Dec '25

03 Dec '25

View online: https://www.drupal.org/sa-contrib-2025-122 Project: Next.js [1] Date: 2025-December-03 Security risk: *Critical* 16 ∕ 25 AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:All [2] Vulnerability: Access bypass Affected versions: <1.6.4 || >=2.0.0 <2.0.1 CVE IDs: CVE-2025-13984 Description: This module enables integration between Next.js and Drupal for headless CMS functionality. When installed, the module automatically enables cross-origin resource sharing (CORS) with insecure default settings (Access-Control-Allow-Origin: *), overriding any services.yml CORS configuration. This allows any origin to make cross-origin requests to the site without administrator knowledge or consent. This vulnerability affects all installations as there are no configuration options to disable this behavior. Solution: There are two steps to resolve the issue: Install the latest version and review your configuration, 1) Update the module: * If you use the Next.js module for Drupal 10 or 11, upgrade to Next.js 2.0.1 [3]. * If you use the Next.js module for Drupal 9 (1.x branch), upgrade to Next.js 1.6.4 [4]. 2) After upgrading, review the CORS configuration in sites/default/services.yml. (See this module's CORS.md for details.). This is especially important if you previously relied on the automatic CORS configuration. Reported By: * Mike Decker (pookmish) [5] Fixed By: * Brian Perry (brianperry) [6] * Rob Decker (rrrob) [7] Coordinated By: * Bram Driesen (bramdriesen) [8] provisional member of the Drupal Security Team * Greg Knaddison (greggles) [9] of the Drupal Security Team * Jess (xjm) [10] of the Drupal Security Team ------------------------------------------------------------------------------ Contribution record [11] [1] https://www.drupal.org/project/next [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/next/releases/2.0.1 [4] https://www.drupal.org/project/next/releases/1.6.4 [5] https://www.drupal.org/u/pookmish [6] https://www.drupal.org/u/brianperry [7] https://www.drupal.org/u/rrrob [8] https://www.drupal.org/u/bramdriesen [9] https://www.drupal.org/u/greggles [10] https://www.drupal.org/u/xjm [11] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

← Newer
1
2
3
4
5
6
7
...
179
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Security-news