- Security-news - lists.drupal.org

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

Tagify - Moderately critical - Cross-site Scripting - SA-CONTRIB-2025-121
by security-news＠drupal.org 03 Dec '25

03 Dec '25

View online: https://www.drupal.org/sa-contrib-2025-121 Project: Tagify [1] Date: 2025-December-03 Security risk: *Moderately critical* 12 ∕ 25 AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:Uncommon [2] Vulnerability: Cross-site Scripting Affected versions: <1.2.44 CVE IDs: CVE-2025-13983 Description: This module enables you to use the Tagify library to enhance text input fields with tag-style UI elements. The module does not sufficiently sanitize the infoLabel value under certain configurations, which can result in a cross-site scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that only uncommon module configurations expose the affected infoLabel output, and an attacker must have user-level access to supply or manipulate this value. Solution: Install the latest version: * If you use the Tagify module for Drupal, upgrade to Tagify 1.2.44 [3]. Reported By: * Drew Webber (mcdruid) [4] of the Drupal Security Team Fixed By: * Bram Driesen (bramdriesen) [5] provisional member of the Drupal Security Team * David Galeano (gxleano) [6] * Lee Rowlands (larowlan) [7] of the Drupal Security Team * Drew Webber (mcdruid) [8] of the Drupal Security Team Coordinated By: * Bram Driesen (bramdriesen) [9] provisional member of the Drupal Security Team * Greg Knaddison (greggles) [10] of the Drupal Security Team * Drew Webber (mcdruid) [11] of the Drupal Security Team * Jess (xjm) [12] of the Drupal Security Team ------------------------------------------------------------------------------ Contribution record [13] [1] https://www.drupal.org/project/tagify [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/tagify/releases/1.2.44 [4] https://www.drupal.org/u/mcdruid [5] https://www.drupal.org/u/bramdriesen [6] https://www.drupal.org/u/gxleano [7] https://www.drupal.org/u/larowlan [8] https://www.drupal.org/u/mcdruid [9] https://www.drupal.org/u/bramdriesen [10] https://www.drupal.org/u/greggles [11] https://www.drupal.org/u/mcdruid [12] https://www.drupal.org/u/xjm [13] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Login Time Restriction - Moderately critical - Cross-Site Request Forgery - SA-CONTRIB-2025-120
by security-news＠drupal.org 03 Dec '25

03 Dec '25

View online: https://www.drupal.org/sa-contrib-2025-120 Project: Login Time Restriction [1] Date: 2025-December-03 Security risk: *Moderately critical* 10 ∕ 25 AC:Basic/A:None/CI:None/II:None/E:Theoretical/TD:All [2] Vulnerability: Cross-Site Request Forgery Affected versions: <1.0.3 CVE IDs: CVE-2025-13982 Description: This module enables you to apply time-based login restrictions and display related warning or logout confirmation pages. The module doesn't sufficiently protect its confirmation routes from cross-site request forgery (CSRF), allowing the logout confirmation route to be triggered without user interaction. Solution: Install the latest version: * If you use the Login Time Restriction module for Drupal, upgrade to Login Time Restriction v1.0.3 [3]. Reported By: * Pierre Rudloff (prudloff) [4] provisional member of the Drupal Security Team Fixed By: * Kunal Singh (kunal_singh) [5] Coordinated By: * Greg Knaddison (greggles) [6] of the Drupal Security Team * Juraj Nemec (poker10) [7] of the Drupal Security Team * Pierre Rudloff (prudloff) [8] provisional member of the Drupal Security Team * Jess (xjm) [9] of the Drupal Security Team ------------------------------------------------------------------------------ Contribution record [10] [1] https://www.drupal.org/project/login_time_restriction [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/login_time_restriction/releases/1.0.3 [4] https://www.drupal.org/u/prudloff [5] https://www.drupal.org/u/kunal_singh [6] https://www.drupal.org/u/greggles [7] https://www.drupal.org/u/poker10 [8] https://www.drupal.org/u/prudloff [9] https://www.drupal.org/u/xjm [10] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

AI (Artificial Intelligence) - Moderately critical - Cross-Site Scripting - SA-CONTRIB-2025-119
by security-news＠drupal.org 03 Dec '25

03 Dec '25

View online: https://www.drupal.org/sa-contrib-2025-119 Project: AI (Artificial Intelligence) [1] Date: 2025-December-03 Security risk: *Moderately critical* 13 ∕ 25 AC:Complex/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2] Vulnerability: Cross-Site Scripting Affected versions: <1.0.7 || >=1.1.0 <1.1.7 || >=1.2.0 <1.2.4 CVE IDs: CVE-2025-13981 Description: This modules provides the ability to chat with an AI Agent using a large-language model (LLM) provider for different purposes. The module doesn’t sufficiently filter LLM responses. This leads to a cross-site scripting (XSS) vulnerability where an attacker can use prompt injections on user-generated content with the LLM as context. Solution: Install the latest version: * If you use the AI module 1.0.x, upgrade to AI 1.0.7 [3] * If you use the AI module 1.1.x, upgrade to AI 1.1.7 [4] * If you use the AI module 1.2.x, upgrade to AI 1.2.4 [5] Reported By: * Drew Webber (mcdruid) [6] of the Drupal Security Team Fixed By: * Marcus Johansson (marcus_johansson) [7] Coordinated By: * Bram Driesen (bramdriesen) [8] provisional member 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/ai [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/ai/releases/1.0.7 [4] https://www.drupal.org/project/ai/releases/1.1.7 [5] https://www.drupal.org/project/ai/releases/1.2.4 [6] https://www.drupal.org/u/mcdruid [7] https://www.drupal.org/u/marcus_johansson [8] https://www.drupal.org/u/bramdriesen [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

CKEditor 5 Premium Features - Moderately critical - Access bypass - SA-CONTRIB-2025-118
by security-news＠drupal.org 03 Dec '25

03 Dec '25

View online: https://www.drupal.org/sa-contrib-2025-118 Project: CKEditor 5 Premium Features [1] Date: 2025-December-03 Security risk: *Moderately critical* 13 ∕ 25 AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:All [2] Vulnerability: Access bypass Affected versions: <1.2.10 || >=1.3.0 <1.3.6 || >=1.4.0 <1.4.3 || >=1.5.0 <1.5.1 || >=1.6.0 <1.6.4 CVE IDs: CVE-2025-13980 Description: The module provides instant integration of the official CKEditor 5 Premium plugins into the Drupal editor configuration. This module has a path traversal vulnerability, which allows an access bypass to restricted image files in the system. This access bypass is possible for any account with a /View published content/ permission, but the risk is mitigated by the fact that only images can be opened. Solution: Install the latest version: * If you use the 10.3 or higher or 11.x versions of Drupal core, upgrade the module to CKEditor 5 Premium Features 1.6.4 [3]. * If you use the 10.0 to 10.2 versions of Drupal core, upgrade the module to CKEditor 5 Premium Features 1.5.1 [4]. * If you use the 9.x version of Drupal core, upgrade the module to CKEditor 5 Premium Features 1.3.6 [5]. A fix was also released to already unsupported branches. However, we recommend to use the latest version that works with the version of Drupal core that you're using: * CKEditor 5 Premium Features 1.4.3 [6]. * CKEditor 5 Premium Features 1.2.10 [7]. After the module is updated, if you are using the Export to Word or Export to PDF plugins, please grant the /Use exporters endpoints/ permission to roles that are allowed to use text formats with export plugins enabled. Reported By: * Wojciech Kukowski (salmonek) [8] Fixed By: * Wojciech Kukowski (salmonek) [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/ckeditor5_premium_features [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/ckeditor5_premium_features/releases/1.6.4 [4] https://www.drupal.org/project/ckeditor5_premium_features/releases/1.5.1 [5] https://www.drupal.org/project/ckeditor5_premium_features/releases/1.3.6 [6] https://www.drupal.org/project/ckeditor5_premium_features/releases/1.4.3 [7] https://www.drupal.org/project/ckeditor5_premium_features/releases/1.2.10 [8] https://www.drupal.org/u/salmonek [9] https://www.drupal.org/u/salmonek [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

Mini site - Moderately critical - Cross-Site Scripting - SA-CONTRIB-2025-117
by security-news＠drupal.org 03 Dec '25

03 Dec '25

View online: https://www.drupal.org/sa-contrib-2025-117 Project: Mini site [1] Date: 2025-December-03 Security risk: *Moderately critical* 14 ∕ 25 AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2] Vulnerability: Cross-Site Scripting Affected versions: <3.0.2 CVE IDs: CVE-2025-13979 Description: This module allows uploading a zip file and extracting its content in the public file directory to serve this content from a Drupal website. These zip files may contain arbitrary HTML or SVG content that could allow cross-site scripting vulnerabilities. While this is an expected feature, the module does not sufficiently restrict this functionality to trusted users with a "restricted access" permission. Users without a restricted permission should not be able to inject arbitrary JavaScript. This vulnerability is mitigated by the fact that an attacker must have a role with the permission /create [bundle] content/ permission. Solution: *Two steps are required.* Install the latest version and adjust configuration: 1) If you use Mini site 2.x or 3.x versions, upgrade to the Mini site 3.0.2 [3]. 2) A new /manage minisites/ permission has been added. This new permission will need to be assigned to a trusted role for the user to be able to upload the zip file. Reported By: * Pierre Rudloff (prudloff) [4] provisional member of the Drupal Security Team Fixed By: * cb_govcms [5] Coordinated By: * Greg Knaddison (greggles) [6] of the Drupal Security Team * Juraj Nemec (poker10) [7] of the Drupal Security Team * Pierre Rudloff (prudloff) [8] provisional member of the Drupal Security Team * Jess (xjm) [9] of the Drupal Security Team ------------------------------------------------------------------------------ Contribution record [10] [1] https://www.drupal.org/project/minisite [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/minisite/releases/3.0.2 [4] https://www.drupal.org/u/prudloff [5] https://www.drupal.org/u/cb_govcms [6] https://www.drupal.org/u/greggles [7] https://www.drupal.org/u/poker10 [8] https://www.drupal.org/u/prudloff [9] https://www.drupal.org/u/xjm [10] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Drupal core - Moderately critical - Information disclosure - SA-CORE-2025-008
by security-news＠drupal.org 13 Nov '25

13 Nov '25

View online: https://www.drupal.org/sa-core-2025-008 Project: Drupal core [1] Date: 2025-November-12 Security risk: *Moderately critical* 10 ∕ 25 AC:Complex/A:None/CI:Some/II:None/E:Theoretical/TD:Uncommon [2] Vulnerability: Information disclosure Affected versions: >= 8.0.0 < 10.4.9 || >= 10.5.0 < 10.5.6 || >= 11.0.0 < 11.1.9 || >= 11.2.0 < 11.2.8 CVE IDs: CVE-2025-13083 Description: The core system module handles downloads of private and temporary files. Contrib modules can define additional kinds of files (schemes) that may also be handled by the system module. In some cases, files may be served with the HTTP header Cache-Control: public when they should be uncacheable. This can lead to some users getting cached versions of files with information they should not be able to access. For example, files may be cached by Varnish or a CDN. This vulnerability is mitigated by the following: 1) Drupal must be configured to handle non-public files using a custom or contributed module providing an additional file scheme. 2) An attacker must know to request a file that has previously been requested by a more-privileged user, and that file must still be cached. Solution: Install the latest version: * If you are using Drupal 10.4, update to Drupal 10.4.9 [3]. * If you are using Drupal 10.5, update to Drupal 10.5.6 [4]. * If you are using Drupal 11.1, update to Drupal 11.1.9 [5]. * If you are using Drupal 11.2, update to Drupal 11.2.8 [6]. Drupal 11.0.x, Drupal 10.3.x, and below are end-of-life and do not receive security coverage. (Drupal 8 [7] and Drupal 9 [8] have both reached end-of-life.) Reported By: * Damien McKenna (damienmckenna) [9] of the Drupal Security Team * tame4tex [10] Fixed By: * Benji Fisher (benjifisher) [11] of the Drupal Security Team * catch (catch) [12] of the Drupal Security Team * Neil Drumm (drumm) [13] of the Drupal Security Team * Lee Rowlands (larowlan) [14] of the Drupal Security Team * Mingsong (mingsong) [15], provisional member of the Drupal Security Team * Mohit Aghera (mohit_aghera) [16] * James Gilliland (neclimdul) [17] of the Drupal Security Team * Juraj Nemec (poker10) [18] of the Drupal Security Team * Jess (xjm) [19] of the Drupal Security Team Coordinated By: * catch (catch) [20] of the Drupal Security Team * Lee Rowlands (larowlan) [21] of the Drupal Security Team * Dave Long (longwave) [22] of the Drupal Security Team * Drew Webber (mcdruid) [23] of the Drupal Security Team * Juraj Nemec (poker10) [24] of the Drupal Security Team ------------------------------------------------------------------------------ Contribution record [25] [1] https://www.drupal.org/project/drupal [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/drupal/releases/10.4.9 [4] https://www.drupal.org/project/drupal/releases/10.5.6 [5] https://www.drupal.org/project/drupal/releases/11.1.9 [6] https://www.drupal.org/project/drupal/releases/11.2.8 [7] https://www.drupal.org/psa-2021-06-29 [8] https://www.drupal.org/psa-2023-11-01 [9] https://www.drupal.org/u/damienmckenna [10] https://www.drupal.org/u/tame4tex [11] https://www.drupal.org/u/benjifisher [12] https://www.drupal.org/u/catch [13] https://www.drupal.org/u/drumm [14] https://www.drupal.org/u/larowlan [15] https://www.drupal.org/u/mingsong [16] https://www.drupal.org/u/mohit_aghera [17] https://www.drupal.org/u/neclimdul [18] https://www.drupal.org/u/poker10 [19] https://www.drupal.org/u/xjm [20] https://www.drupal.org/u/catch [21] https://www.drupal.org/u/larowlan [22] https://www.drupal.org/u/longwave [23] https://www.drupal.org/u/mcdruid [24] https://www.drupal.org/u/poker10 [25] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Drupal core - Moderately critical - Defacement - SA-CORE-2025-007
by security-news＠drupal.org 13 Nov '25

13 Nov '25

View online: https://www.drupal.org/sa-core-2025-007 Project: Drupal core [1] Date: 2025-May-29 Security risk: *Moderately critical* 10 ∕ 25 AC:Basic/A:None/CI:None/II:None/E:Theoretical/TD:All [2] Vulnerability: Defacement Affected versions: >= 8.0.0 < 10.4.9 || >= 10.5.0 < 10.5.6 || >= 11.0.0 < 11.1.9 || >= 11.2.0 < 11.2.8 CVE IDs: CVE-2025-13082 Description: By generating and tricking a user into visiting a malicious URL, an attacker can perform site defacement. The defacement is not stored and is only present when the URL has been crafted for that purpose. Only the defacement is present, so no other site content (such as branding) is rendered. Solution: Install the latest version: * If you are using Drupal 10.4, update to Drupal 10.4.9 [3]. * If you are using Drupal 10.5, update to Drupal 10.5.6 [4]. * If you are using Drupal 11.1, update to Drupal 11.1.9 [5]. * If you are using Drupal 11.2, update to Drupal 11.2.8 [6]. Drupal 11.0.x, Drupal 10.3.x, and below are end-of-life and do not receive security coverage. (Drupal 8 [7] and Drupal 9 [8] have both reached end-of-life.) Reported By: * Kevin Quillen (kevinquillen) [9] Fixed By: * Benji Fisher (benjifisher) [10] of the Drupal Security Team * Neil Drumm (drumm) [11] of the Drupal Security Team * Greg Knaddison (greggles) [12] of the Drupal Security Team * Lee Rowlands (larowlan) [13] of the Drupal Security Team * Drew Webber (mcdruid) [14] of the Drupal Security Team * Mingsong (mingsong) [15], provisional member of the Drupal Security Team * Juraj Nemec (poker10) [16] of the Drupal Security Team * Ra Mänd (ram4nd) [17], provisional member of the Drupal Security Team * Jess (xjm) [18] of the Drupal Security Team Coordinated By: * catch (catch) [19] of the Drupal Security Team * Lee Rowlands (larowlan) [20] of the Drupal Security Team * Dave Long (longwave) [21] of the Drupal Security Team * Juraj Nemec (poker10) [22] of the Drupal Security Team Security issue: https://git.drupalcode.org/security/7-drupal-security/-/issues/1 [23] ------------------------------------------------------------------------------ Contribution record [24] [1] https://www.drupal.org/project/drupal [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/drupal/releases/10.4.9 [4] https://www.drupal.org/project/drupal/releases/10.5.6 [5] https://www.drupal.org/project/drupal/releases/11.1.9 [6] https://www.drupal.org/project/drupal/releases/11.2.8 [7] https://www.drupal.org/psa-2021-06-29 [8] https://www.drupal.org/psa-2023-11-01 [9] https://www.drupal.org/u/kevinquillen [10] https://www.drupal.org/u/benjifisher [11] https://www.drupal.org/u/drumm [12] https://www.drupal.org/u/greggles [13] https://www.drupal.org/u/larowlan [14] https://www.drupal.org/u/mcdruid [15] https://www.drupal.org/u/mingsong [16] https://www.drupal.org/u/poker10 [17] https://www.drupal.org/u/ram4nd [18] https://www.drupal.org/u/xjm [19] https://www.drupal.org/u/catch [20] https://www.drupal.org/u/larowlan [21] https://www.drupal.org/u/longwave [22] https://www.drupal.org/u/poker10 [23] https://git.drupalcode.org/security/7-drupal-security/-/issues/1 [24] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0