- Security-news - lists.drupal.org

Facets - Moderately critical - Cross Site Scripting - SA-CONTRIB-2025-100
by security-news＠drupal.org 27 Aug '25

27 Aug '25

View online: https://www.drupal.org/sa-contrib-2025-100 Project: Facets [1] Date: 2025-August-27 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: <2.0.10 || >=3.0.0 <3.0.1 CVE IDs: CVE-2025-9549 Description: This module enables you to to easily create and manage faceted search interfaces. The module doesn’t sufficiently filter certain user-provided text leading to a cross site scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with the permission “administer facets”. *CVSS risk score (experimental [3]) 4.8 / Medium* CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:L/SI:N/SA:N [4] Solution: Install the latest version: * If you use the Facets module for Drupal 8.x or higher, upgrade to Facets 2.0.10 [5] or Facets 3.0.1 [6] Reported By: * Pierre Rudloff (prudloff) [7] Fixed By: * Joris Vercammen (borisson_) [8] * Thomas Seidl (drunken monkey) [9] * Pierre Rudloff (prudloff) [10], provisional member of the Drupal Security Team Coordinated By: * Damien McKenna (damienmckenna) [11] of the Drupal Security Team * Ivo Van Geertruyen (mr.baileys) [12] of the Drupal Security Team * Pierre Rudloff (prudloff) [13], provisional member of the Drupal Security Team * Drew Webber (mcdruid) [14] of the Drupal Security Team [1] https://www.drupal.org/project/facets [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/securitydrupalorg/issues/3442181 [4] https://www.first.org/cvss/calculator/4-0#CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P… [5] https://www.drupal.org/project/facets/releases/2.0.10 [6] https://www.drupal.org/project/facets/releases/3.0.1 [7] https://www.drupal.org/u/prudloff [8] https://www.drupal.org/u/borisson_ [9] https://www.drupal.org/u/drunken-monkey [10] https://www.drupal.org/u/prudloff [11] https://www.drupal.org/u/damienmckenna [12] https://www.drupal.org/u/mrbaileys [13] https://www.drupal.org/u/prudloff [14] https://www.drupal.org/u/mcdruid

1 0

Facets - Moderately critical - Information Disclosure - SA-CONTRIB-2025-099
by security-news＠drupal.org 27 Aug '25

27 Aug '25

View online: https://www.drupal.org/sa-contrib-2025-099 Project: Facets [1] Date: 2025-August-27 Security risk: *Moderately critical* 11 ∕ 25 AC:Complex/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] Vulnerability: Information Disclosure Affected versions: <2.0.10 || >=3.0.0 <3.0.1 CVE IDs: CVE-2025-9549 Description: This module enables you to to easily create and manage faceted search interfaces. The module doesn't sufficiently check access to entities when they are displayed as facets. This vulnerability is mitigated by the fact that only sites that show facets with entity labels (like taxonomy terms) are affected, and only if some of those entities are unpublished or have other access restrictions. *CVSS risk score (experimental [3]) 6.9 / Medium* CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N [4] Solution: Install the latest version: * If you use the Facets module for Drupal 8.x or higher, upgrade to Facets 2.0.10 [5] or Facets 3.0.1 [6] Reported By: * Damien McKenna (damienmckenna) [7] of the Drupal Security Team Fixed By: * Benji Fisher (benjifisher) [8] of the Drupal Security Team * Joris Vercammen (borisson_) [9] * Damien McKenna (damienmckenna) [10] of the Drupal Security Team * Thomas Seidl (drunken monkey) [11] * Jimmy Henderickx (strykaizer) [12] Coordinated By: * Benji Fisher (benjifisher) [13] of the Drupal Security Team * Damien McKenna (damienmckenna) [14] of the Drupal Security Team * Greg Knaddison (greggles) [15] of the Drupal Security Team * Drew Webber (mcdruid) [16] of the Drupal Security Team * Cathy Theys (yesct) [17] of the Drupal Security Team [1] https://www.drupal.org/project/facets [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/securitydrupalorg/issues/3442181 [4] https://www.first.org/cvss/calculator/4-0#CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N… [5] https://www.drupal.org/project/facets/releases/2.0.10 [6] https://www.drupal.org/project/facets/releases/3.0.1 [7] https://www.drupal.org/u/damienmckenna [8] https://www.drupal.org/u/benjifisher [9] https://www.drupal.org/u/borisson_ [10] https://www.drupal.org/u/damienmckenna [11] https://www.drupal.org/u/drunken-monkey [12] https://www.drupal.org/u/strykaizer [13] https://www.drupal.org/u/benjifisher [14] https://www.drupal.org/u/damienmckenna [15] https://www.drupal.org/u/greggles [16] https://www.drupal.org/u/mcdruid [17] https://www.drupal.org/u/yesct

1 0

Authenticator Login - Moderately critical - Access bypass - SA-CONTRIB-2025-098
by security-news＠drupal.org 27 Aug '25

27 Aug '25

View online: https://www.drupal.org/sa-contrib-2025-098 Project: Authenticator Login [1] Date: 2025-August-27 Security risk: *Moderately critical* 13 ∕ 25 AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:Default [2] Vulnerability: Access bypass Affected versions: <2.1.8 CVE IDs: CVE-2025-8093 Description: This module allows users to setup two-factor authentication (2FA) using authenticator apps for enhanced login security. The module did not protect all possible login paths provided by core modules. *CVSS risk score (experimental [3]) 6.3 / Medium* CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N [4] Solution: Install the latest version: * If you use the Alogin module for Drupal 10^, upgrade to Alogin 2.1.8 [5] Reported By: * Pierre Rudloff (prudloff) [6] Fixed By: * Ahmed Raza (ahmed.raza) [7] * Pierre Rudloff (prudloff) [8], provisional member of the Drupal Security Team Coordinated By: * Damien McKenna (damienmckenna) [9] of the Drupal Security Team * Greg Knaddison (greggles) [10] of the Drupal Security Team * Drew Webber (mcdruid) [11] of the Drupal Security Team * Juraj Nemec (poker10) [12] of the Drupal Security Team * Cathy Theys (yesct) [13] of the Drupal Security Team [1] https://www.drupal.org/project/alogin [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/securitydrupalorg/issues/3442181 [4] https://www.first.org/cvss/calculator/4-0#CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N… [5] https://www.drupal.org/project/alogin/releases/2.1.8 [6] https://www.drupal.org/u/prudloff [7] https://www.drupal.org/u/ahmedraza [8] https://www.drupal.org/u/prudloff [9] https://www.drupal.org/u/damienmckenna [10] https://www.drupal.org/u/greggles [11] https://www.drupal.org/u/mcdruid [12] https://www.drupal.org/u/poker10 [13] https://www.drupal.org/u/yesct

1 0

Layout Builder Advanced Permissions - Moderately critical - Access bypass - SA-CONTRIB-2025-097
by security-news＠drupal.org 13 Aug '25

13 Aug '25

View online: https://www.drupal.org/sa-contrib-2025-097 Project: Layout Builder Advanced Permissions [1] Date: 2025-August-13 Security risk: *Moderately critical* 10 ∕ 25 AC:Basic/A:User/CI:None/II:Some/E:Theoretical/TD:Default [2] Vulnerability: Access bypass Affected versions: 2.2.0 CVE IDs: CVE-2025-8996 Description: The Layout Builder Advanced Permissions module enables you to have fine grained control over who can do what in editing pages built with Layout Builder. The module doesn't sufficiently control access for adding sections in the submodule. This vulnerability is mitigated by the fact that an attacker must have a role with a specific set of permissions: * Node: View published content * Node: (Your content type): Create new content * Node: (Your content type): Edit any content * Layout builder: (Your content type): Configure layout overrides for content items that the user can edit * Layout builder advanced permissions: Access Layout Builder page Solution: Install the latest version: * If you use the Layout Builder Advanced Permissions module, upgrade to Layout Builder Advanced Permissions 2.2.1 [3] Reported By: * Eelke Blok (eelkeblok) [4] * Michael Whittaker (mrwhittaker) [5] Fixed By: * Eelke Blok (eelkeblok) [6] * Sorin Dediu (sdstyles) [7] * Sean Blommaert (seanb) [8] Coordinated By: * Anna Kalata (akalata) [9] * Damien McKenna (damienmckenna) [10] of the Drupal Security Team * Greg Knaddison (greggles) [11] of the Drupal Security Team * Juraj Nemec (poker10) [12] of the Drupal Security Team * Cathy Theys (yesct) [13] of the Drupal Security Team [1] https://www.drupal.org/project/layout_builder_perms [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/layout_builder_perms/releases/2.2.1 [4] https://www.drupal.org/u/eelkeblok [5] https://www.drupal.org/u/mrwhittaker [6] https://www.drupal.org/u/eelkeblok [7] https://www.drupal.org/u/sdstyles [8] https://www.drupal.org/u/seanb [9] https://www.drupal.org/u/akalata [10] https://www.drupal.org/u/damienmckenna [11] https://www.drupal.org/u/greggles [12] https://www.drupal.org/u/poker10 [13] https://www.drupal.org/u/yesct

1 0

Authenticator Login - Highly critical - Access bypass - SA-CONTRIB-2025-096
by security-news＠drupal.org 13 Aug '25

13 Aug '25

View online: https://www.drupal.org/sa-contrib-2025-096 Project: Authenticator Login [1] Date: 2025-August-13 Security risk: *Highly critical* 21 ∕ 25 AC:Basic/A:None/CI:All/II:All/E:Proof/TD:All [2] Vulnerability: Access bypass Affected versions: <2.1.4 CVE IDs: CVE-2025-8995 Description: This module enables users to setup two-factor authentication (2FA) using authenticator apps for enhanced login security. The module alters the standard Drupal login form to use AJAX callbacks for handling authentication flow. The module doesn't sufficiently validate authentication under specific conditions, allowing an attacker to log in as any account where they know the username. This vulnerability is mitigated by the fact that an attacker must make a series of requests to trigger the necessary conditions that allow authentication byass. The series of requests could alert a site owner that they are being attacked; however, the number of requests necessary to trigger the conditions is usually quite small (the number depends on site configuration, by default it is 5). Solution: Install the latest version: * If you use the alogin module for Drupal 10^, upgrade to the latest version or at least Alogin 2.1.5 [3] /Note: the fix is in a tag in git for 2.1.4 however there is no release for that tag. The fix is also in 2.1.5 relase./ Reported By: * Pierre Rudloff (prudloff) [4] Fixed By: * Ahmed Raza (ahmed.raza) [5] Coordinated By: * Damien McKenna (damienmckenna) [6] of the Drupal Security Team * Dan Smith (galooph) [7] of the Drupal Security Team * Greg Knaddison (greggles) [8] of the Drupal Security Team * Cathy Theys (yesct) [9] of the Drupal Security Team [1] https://www.drupal.org/project/alogin [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/alogin/releases/2.1.5 [4] https://www.drupal.org/u/prudloff [5] https://www.drupal.org/u/ahmedraza [6] https://www.drupal.org/u/damienmckenna [7] https://www.drupal.org/u/galooph [8] https://www.drupal.org/u/greggles [9] https://www.drupal.org/u/yesct

1 0

AI SEO Link Advisor - Less critical - Server-side Request Forgery - SA-CONTRIB-2025-095
by security-news＠drupal.org 06 Aug '25

06 Aug '25

View online: https://www.drupal.org/sa-contrib-2025-095 Project: AI SEO Link Advisor [1] Date: 2025-August-06 Security risk: *Less critical* 8 ∕ 25 AC:Basic/A:User/CI:None/II:None/E:Theoretical/TD:All [2] Vulnerability: Server-side Request Forgery Affected versions: <1.0.6 CVE IDs: CVE-2025-8675 Description: This module enables you to provide SEO analysis and recommendations for a given URL. The module doesn't sufficiently sanitize user-supplied URLs, leading to a Server-side request forgery (SSRF) vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "access seo analyzer". Solution: Install the latest version: * If you use the AI SEO Link Advisor module 1.0.x, upgrade to AI SEO Link Advisor 1.0.6 [3] Reported By: * Alberto Cocchiara (bigbabert) [4] * Conrad Lara (cmlara) [5] Fixed By: * Alberto Cocchiara (bigbabert) [6] * Conrad Lara (cmlara) [7] * Vishal Kadam (vishal.kadam) [8] Coordinated By: * Benji Fisher (benjifisher) [9] of the Drupal Security Team * catch (catch) [10] of the Drupal Security Team * Damien McKenna (damienmckenna) [11] of the Drupal Security Team * Greg Knaddison (greggles) [12] of the Drupal Security Team [1] https://www.drupal.org/project/ai_seo_link_advisor [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/ai_seo_link_advisor/releases/1.0.6 [4] https://www.drupal.org/u/bigbabert [5] https://www.drupal.org/u/cmlara [6] https://www.drupal.org/u/bigbabert [7] https://www.drupal.org/u/cmlara [8] https://www.drupal.org/u/vishalkadam [9] https://www.drupal.org/u/benjifisher [10] https://www.drupal.org/u/catch [11] https://www.drupal.org/u/damienmckenna [12] https://www.drupal.org/u/greggles

1 0

GoogleTag Manager - Moderately critical - Cross-site scripting - SA-CONTRIB-2025-094
by security-news＠drupal.org 30 Jul '25

30 Jul '25

View online: https://www.drupal.org/sa-contrib-2025-094 Project: GoogleTag Manager [1] Date: 2025-July-30 Security risk: *Moderately critical* 11 ∕ 25 AC:Complex/A:Admin/CI:Some/II:Some/E:Theoretical/TD:Default [2] Vulnerability: Cross-site scripting Affected versions: <1.10.0 CVE IDs: CVE-2025-8362 Description: This module enables you to integrate Google Tag Manager (GTM) into your Drupal site by allowing administrators to configure and embed GTM container snippets. The module doesn't sufficiently sanitize the GTM container ID under the scenario where a user with the /Administer gtm/ permission enters malicious input into the /GTM-ID/ field. This value is directly inserted into a tag, making the site vulnerable to Cross-site Scripting (XSS) attacks. This vulnerability is mitigated by the fact that an attacker must have a role with the permission /Administer gtm/, and the input field is limited to 20 characters. Solution: Install the latest version: If you use the Google Tag Manager module for Drupal 8.x, upgrade to Google Tag Manager 8.x-1.10 [3]. The new version includes validation to prevent injection and restricts risky inputs. Additionally, site administrators should review which roles have the /Administer gtm/ permission at /admin/people/permissions. Reported By: * Pierre Rudloff (prudloff) [4], provisional member of the Drupal Security Team Fixed By: * Anatoly Politsin (apolitsin) [5] * Pierre Rudloff (prudloff) [6], provisional member of the Drupal Security Team Coordinated By: * Ivo Van Geertruyen (mr.baileys) [7] of the Drupal Security Team * Juraj Nemec (poker10) [8] of the Drupal Security Team * Jess (xjm) [9] of the Drupal Security Team [1] https://www.drupal.org/project/gtm [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/gtm/releases/8.x-1.10 [4] https://www.drupal.org/u/prudloff [5] https://www.drupal.org/u/apolitsin [6] https://www.drupal.org/u/prudloff [7] https://www.drupal.org/u/mrbaileys [8] https://www.drupal.org/u/poker10 [9] https://www.drupal.org/u/xjm

1 0

Config Pages - Moderately critical - Access bypass - SA-CONTRIB-2025-093
by security-news＠drupal.org 30 Jul '25

30 Jul '25

View online: https://www.drupal.org/sa-contrib-2025-093 Project: Config Pages [1] Date: 2025-July-30 Security risk: *Moderately critical* 12 ∕ 25 AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:Uncommon [2] Vulnerability: Access bypass Affected versions: <2.18.0 CVE IDs: CVE-2025-8361 Description: This module enables you to access an edit page for a config page. The module doesn't sufficiently check the access permissions (hook_ENTITY_TYPE_access() wasn't taken into account). This vulnerability is mitigated by the fact that an attacker must have a role with the permission "edit ID config page" and that it only affects sites that have access restricted via the hook_ENTITY_TYPE_access() hook. Solution: Install the latest version: * If you use the Config Pages module, upgrade to Config Pages 8.x-2.18 [3]. Reported By: * Pierre Rudloff (prudloff) [4], provisional member of the Drupal Security Team Fixed By: * Pierre Rudloff (prudloff) [5], provisional member of the Drupal Security Team * Alexander Shumenko (shumer) [6] Coordinated By: * Greg Knaddison (greggles) [7] of the Drupal Security Team * Heine Deelstra (heine) [8] of the Drupal Security Team * Jess (xjm) [9] of the Drupal Security Team [1] https://www.drupal.org/project/config_pages [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/config_pages/releases/8.x-2.18 [4] https://www.drupal.org/u/prudloff [5] https://www.drupal.org/u/prudloff [6] https://www.drupal.org/u/shumer [7] https://www.drupal.org/u/greggles [8] https://www.drupal.org/u/heine [9] https://www.drupal.org/u/xjm

1 0

COOKiES Consent Management - Moderately critical - Cross-site Scripting - SA-CONTRIB-2025-092
by security-news＠drupal.org 23 Jul '25

23 Jul '25

View online: https://www.drupal.org/sa-contrib-2025-092 Project: COOKiES Consent Management [1] Date: 2025-July-23 Security risk: *Moderately critical* 12 ∕ 25 AC:Complex/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2] Vulnerability: Cross-site Scripting Affected versions: <1.2.16 CVE IDs: CVE-2025-8092 Description: This module allows you to manage video media items using the COOKiES module (disabling external video elements). These elements will be enabled again, once the COOKiES banner is accepted. The module doesn't sufficiently check whether to convert "data-src" attributes to "src" when their value might contain malicious content under the scenario, that module specific classes are set on the HTML element. This vulnerability is mitigated by the fact that an attacker must have the correct permissions to have a specific HTML element display for all users, and this HTML element needs to have a specific class set. Solution: Install the latest version: * If you use the COOKiES Video submodule for Drupal upgrade to COOKiES 1.2.16 [3] Reported By: * Pierre Rudloff (prudloff) [4] provisional member of the Drupal Security Team Fixed By: * Joshua Sedler (grevil) [5] * Joachim Feltkamp (jfeltkamp) [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 * Cathy Theys (yesct) [10] of the Drupal Security Team [1] https://www.drupal.org/project/cookies [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/cookies/releases/1.2.16 [4] https://www.drupal.org/u/prudloff [5] https://www.drupal.org/u/grevil [6] https://www.drupal.org/u/jfeltkamp [7] https://www.drupal.org/u/greggles [8] https://www.drupal.org/u/poker10 [9] https://www.drupal.org/u/prudloff [10] https://www.drupal.org/u/yesct

1 0

Real-time SEO for Drupal - Moderately critical - Cross Site Scripting - SA-CONTRIB-2025-091
by security-news＠drupal.org 16 Jul '25

16 Jul '25

View online: https://www.drupal.org/sa-contrib-2025-091 Project: Real-time SEO for Drupal [1] Date: 2025-July-16 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: <2.2.0 CVE IDs: CVE-2025-7716 Description: This module enables you to analyze the content that you're authoring for a website. It shows you a preview of what a search result might look like. The module doesn't sufficiently escape the metadata from content while rendering the preview, opening up the possibility of a XSS attack. This vulnerability is mitigated by the fact that an attacker must be able to author content that is analyzed by the Real-Time SEO module. Solution: Install the latest version: * Upgrade to yoast_seo 8.x-2.2 [3]. Reported By: * Pierre Rudloff (prudloff) [4], provisional member of the Drupal Security Team. Fixed By: * Alexander Varwijk (kingdutch) [5] * Pierre Rudloff (prudloff) [6], provisional member of the Drupal Security Team. Coordinated By: * Damien McKenna (damienmckenna) [7] of the Drupal Security Team * Greg Knaddison (greggles) [8] of the Drupal Security Team * Pierre Rudloff (prudloff), provisional member of the Drupal Security Team [9] * Jess (xjm) [10] of the Drupal Security Team [1] https://www.drupal.org/project/yoast_seo [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/yoast_seo/releases/8.x-2.2 [4] https://www.drupal.org/u/prudloff [5] https://www.drupal.org/u/kingdutch [6] https://www.drupal.org/u/prudloff [7] https://www.drupal.org/u/damienmckenna [8] https://www.drupal.org/u/greggles [9] https://www.drupal.org/u/prudloff [10] https://www.drupal.org/u/xjm

1 0