Drupal Security
AI (Artificial Intelligence) - Critical - Cross Site Request Forgery - SA-CONTRIB-2025-003
The Drupal AI module provides a framework for easily integrating Artificial Intelligence on any Drupal site using any kind of AI (from multiple vendors). The sub-modules AI Chatbot and AI Assistants API allow users to interact with the Drupal site via a 'chat' interface.
The AI Chatbot module doesn't protect against Cross Site Request Forgeries in the Deepchat chatbot. This could allow an attacker to craft a scenario that can forge a request on behalf of a privileged user. When combined with the AI Search submodule, this could result in the AI Assistant exposing indexed data that the attacker should not have access to. When combined with the external AI Agent module, this could result in the AI Assistant exposing and allowing modification of site configuration of fields, content types, and vocabularies. Sites with custom built agents, with more privileged access, could be at greater risk from an exploit of this vulnerability.
This vulnerability is mitigated by:
- The targeted user needs to have an active session with a role with the "access deepchat api" permission and permission to assistants.
- To extract data, the target site must have a permissive CORS policy allowing the attacking site to read the result of a cross origin request.
- To modify data, the targeted user must have permission to use the configured agents.
Install the latest version:
- If you use the AI module, upgrade to AI 1.0.2
If you cannot update, you can can uninstall the AI Chatbot sub-module.
Reported By: Fixed By: Coordinated By:- Greg Knaddison of the Drupal Security Team
- Drew Webber of the Drupal Security Team
- Juraj Nemec of the Drupal Security Team
Profile Private - Critical - Unsupported - SA-CONTRIB-2025-002
The security team is marking this project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, please read: https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...
Solution:If you use this project, you should uninstall it. To take over maintainership, please read https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...
Reported By: Coordinated By:- Ivo Van Geertruyen of the Drupal Security Team
- Cathy Theys of the Drupal Security Team
- Greg Knaddison of the Drupal Security Team
Email TFA - Moderately critical - Access bypass - SA-CONTRIB-2025-001
This module enables you to do Two-Factor Authentication by email, using a user registered email to send a verification code to the user's email every time the user tries to log in to your site.
The module did not sufficiently protect against brute force attacks, allowing an attacker to bypass the second factor.
This vulnerability is mitigated by the fact the attacker must be able to present the username and first factor (i.e. password).
Solution:Install the latest version:
- If you use the Email TFA module, upgrade to Email TFA 2.0.3
- Greg Knaddison of the Drupal Security Team
- Juraj Nemec of the Drupal Security Team
Drupal 7 End of Life - PSA-2025-01-06
Drupal core version 7 has reached end of life, and is no longer community supported on Drupal.org. This means that new releases of Drupal 7 core and contributed projects will no longer happen on Drupal.org and community support is no longer provided.
What this means for you:
- Any vulnerabilities that impact Drupal 7 may be released and made public without Security Advisories or warnings. Please continue to follow the process outlined in: Report a security issue
- Drupal 7 will no longer be supported. There will be no more core commits on Drupal 7.x to the official repository. The community will no longer be creating new Drupal 7 releases, fixing bugs in existing projects, writing documentation, etc. around Drupal 7.
- The Drupal Security Team will no longer provide support or Security Advisories for Drupal 7 and Drupal-7-compatible contributed projects.
- All Drupal 7 releases on project pages will be flagged as not supported.
At some point in the future, update status and packages.drupal.org/7 will stop working for Drupal 7 sites.
Solution:
You can learn about upgrading Drupal and migrations or read about other options.
Open Social - Moderately critical - Access bypass - SA-CONTRIB-2024-076
Open Social is a Drupal distribution for online communities, which ships with a default (optional) module social_file_private to ensure the images and files provided by the distribution are stored in the private instead of the public filesystem.
For installations of Open Social prior to version 11.8.0, after updating to 11.8.0 or higher, newly uploaded files were no longer stored in the private file system as intended. Instead, they were stored in the public file system.
Solution:Install the latest version and make sure to run the update hooks.
- If you use Open Social 12.3.x upgrade to Open Social 12.3.10
- If you use Open Social 12.4.x upgrade to Open Social 12.4.9
Note: If some files were uploaded during that time and became unused, the update hook cannot move them. These files will require manual cleanup. Read the module release notes linked above for advice on how to handle that situation.
Reported By: Fixed By: Coordinated By:- Greg Knaddison of the Drupal Security Team
Allow All File Extensions for file fields - Critical - Unsupported - SA-CONTRIB-2024-075
The security team is marking this project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, please read: https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...
Solution:If you use this project, you should uninstall it. To take over maintainership, please read https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...
Git Utilities for Drupal - Critical - Unsupported - SA-CONTRIB-2024-074
The security team is marking this project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, please read: https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...
Solution:If you use this project, you should uninstall it. To take over maintainership, please read https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...
Login Disable - Critical - Access bypass - SA-CONTRIB-2024-073
This module enables you to prevent existing users from logging in to your Drupal site unless they know the secret key to add to the end of the ?q=user login form page.
The Login Disable module does not correctly prevent a user with a disabled login from logging in, allowing those users to by-pass the protection offered by the module.
This vulnerability is mitigated by the fact that an attacker must already have a user account to log in. This bug therefore allows users to log in even if their login is disabled.
Solution:Install the latest version:
- If you use the Login Disable module for Drupal 9.x / 10.x, upgrade to Login Disable 2.1.1
The Drupal 7 version of the module is not affected.
Reported By: Fixed By: Coordinated By:- Ivo Van Geertruyen of the Drupal Security Team
- Greg Knaddison of the Drupal Security Team
- Benji Fisher of the Drupal Security Team
Browser Back Button - Moderately critical - Cross site scripting - SA-CONTRIB-2024-072
This module provides a block that renders a link providing the functionality of a browser's back button.
The module does not sufficiently escape text entered by an administrator, resulting in a cross scripting vulnerability.
This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer blocks".
Solution:Install the latest version:
- If you use the Browser Back Button module for Drupal 9.x/10.x, upgrade to Browser Back Button 2.0.2
- Ivo Van Geertruyen of the Drupal Security Team
Entity Form Steps - Moderately critical - Cross site scripting - SA-CONTRIB-2024-071
This module allows a site builder to create multi-step entity forms leveraging the Field Group field type plugins.
The module doesn't escape plain text administrative configurations. An attacker with admin access could inject arbitrary JavaScript code.
This vulnerability is mitigated by the fact that an attacker must have a role with the 'administer [entity_type] form display' permission allowing access to configure entity form displays.
Solution:Install the latest version:
- If you use the Entity Form Steps module for Drupal 9.x/10.x, upgrade to Entity Form Steps 1.1.4
- Ivo Van Geertruyen of the Drupal Security Team
Minify JS - Moderately critical - Cross site request forgery - SA-CONTRIB-2024-070
The Minify JS module allows a site administrator to minify all javascript files that exist in the site's code base and use those minified files on the front end of the website.
Several administrator routes are unprotected against Cross-Site Request Forgery (CRSF) attacks.
Solution:Install the latest version:
- If you use the Minify JS module for Drupal 7.x, upgrade to Minify JS 7.x-1.11
- If you use the Minify JS module for Drupal 8.x, upgrade to Minify JS 3.0.3
- Ivo Van Geertruyen of the Drupal Security Team
- Scott Joudry
- Ivo Van Geertruyen of the Drupal Security Team
Download All Files - Critical - Access bypass - SA-CONTRIB-2024-069
This module provides a field formatter for the field type 'file' called `Table of files with download all link` .
The module had vulnerabilities allowing a user to download files they normally should not be able to download.
Solution:Install the latest version:
- If you use the Download All Files module, upgrade to 2.0.2 version
- Greg Knaddison of the Drupal Security Team
- Damien McKenna of the Drupal Security Team
- Ivo Van Geertruyen of the Drupal Security Team
Pages Restriction Access - Critical - Access bypass - SA-CONTRIB-2024-068
Module to restrict access from anonymous and regular users to configured pre-defined pages.
The module does not adequately handle protecting certain types of URLs.
Solution:Install the latest version:
- If you use the Pages Restriction Access for Drupal 8.x or higher, upgrade to Pages Restriction Access for Drupal 2.0.3
- Pierre Rudloff
- Ivo Van Geertruyen of the Drupal Security Team
- Greg Knaddison of the Drupal Security Team
- Damien McKenna of the Drupal Security Team
- Juraj Nemec of the Drupal Security Team
- Ivo Van Geertruyen of the Drupal Security Team
OAuth & OpenID Connect Single Sign On – SSO (OAuth/OIDC Client) - Critical - Cross Site Scripting - SA-CONTRIB-2024-067
This module enables you to authenticate users through an Identity Provider (IdP) or OAuth Server, allowing them to log in to your Drupal site.
The module does not sufficiently escape query parameters sent to the callback URL when displaying error messages, particularly if the code parameter is missing in the response.
Solution:Install the latest version:
- If you use the OAuth & OpenID Connect Single Sign On – SSO (OAuth/OIDC Client) module 8.x-3.x for Drupal 9 and Drupal 10, upgrade to miniorange_oauth_client 8.x-3.44 .
- If you use the OAuth & OpenID Connect Single Sign On – SSO (OAuth/OIDC Client) module 4.x for Drupal 9, Drupal 10 and Drupal 11, upgrade to miniorange_oauth_client 4.0.19.
- If you use the OAuth & OpenID Connect Single Sign On – SSO (OAuth/OIDC Client) module 7.x-1.x for Drupal 7, upgrade to miniorange_oauth_client 7.x-1.355.
- Borut Piletic
- singh_ankit
- Ivo Van Geertruyen of the Drupal Security Team
- Greg Knaddison of the Drupal Security Team
- Damien McKenna of the Drupal Security Team
Print Anything - Critical - Unsupported - SA-CONTRIB-2024-066
The security team is marking this project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, please read: https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...
Solution:If you use this project, you should uninstall it. To take over maintainership, please read https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...
Reported By:- Drew Webber of the Drupal Security Team
Megamenu Framework - Critical - Unsupported - SA-CONTRIB-2024-065
The security team is marking this project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, please read: https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...
Solution:If you use this project, you should uninstall it. To take over maintainership, please read https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...
Reported By:- Drew Webber of the Drupal Security Team
Tarte au Citron - Moderately critical - Cross Site Scripting - SA-CONTRIB-2024-064
This module integrates Tarte au citron JS library with Drupal and prevent services to be loaded without user consent. Administrators can enable and configure services which will be managed by Tarte au citron.
When Google Tag Manager (GTM) service is enabled, an attacker can load a GTM container that can completely change the page or insert malicious JS.
This vulnerability is mitigated by the fact that the attacker must have a role with the permission "administer tarte au citron".
Solution:Install the latest version and confirm only trusted roles have the "Administer Tarte au citron" permission.
- If you use the Tarte au citron module for Drupal 10.x, upgrade to Tarte au citron 2.0.5
- Greg Knaddison of the Drupal Security Team
- Juraj Nemec of the Drupal Security Team
- cilefen of the Drupal Security Team
Eloqua - Moderately critical - Arbitrary PHP code execution - SA-CONTRIB-2024-063
This module integrates webforms with eloqua, an automated marketing and demand generation software built to improve the quality and quantity of customers' sales leads and streamline their sales processes.
In certain cases the module doesn't sufficiently sanitize data before passing it to PHP's unserialize() function, which could result in Remote Code Execution via PHP Object Injection.
This vulnerability is mitigated by the fact that an attack must operate with the permission "access administration pages", however this could be the case if this issue were combined with others in an "attack chain".
Solution:Install the latest version:
- If you use the Eloqua module for Drupal 7.x, upgrade to Eloqua 7.x-1.15
- Drew Webber of the Drupal Security Team
- Greg Knaddison of the Drupal Security Team
Mailjet - Moderately critical - Arbitrary PHP code execution - SA-CONTRIB-2024-062
This module for Drupal provides complete control of Email settings with Drupal and Mailjet.
In certain cases the module doesn't securely pass data to PHP's unserialize() function, which could result in Remote Code Execution via PHP Object Injection.
This vulnerability is mitigated by the fact that an attack must operate with the permission "administer mailjet module", however this could be the case if this issue were combined with others in an "attack chain".
Solution:Install the latest version:
- Upgrade to Mailjet 4.0.1
- For Drupal 7.x, upgrade to Mailjet 7.x-2.23
- Drew Webber of the Drupal Security Team
- Drew Webber of the Drupal Security Team
- Bohdan Artemchuk
- Drew Webber of the Drupal Security Team
Drupal core - Moderately critical - Gadget chain - SA-CORE-2024-008
Drupal core contains a potential PHP Object Injection vulnerability that (if combined with another exploit) could lead to Remote Code Execution. It is not directly exploitable.
This issue is mitigated by the fact that in order for it to be exploitable, a separate vulnerability must be present to allow an attacker to pass unsafe input to unserialize(). There are no such known exploits in Drupal core.
To help protect against this potential vulnerability, some additional checks have been added to Drupal core's database code. If you use a third-party database driver, check the release notes for additional configuration steps that may be required in certain cases.
Solution:Install the latest version:
- If you are using Drupal 7, update to Drupal 7.102.
- If you are using Drupal 10.2, update to Drupal 10.2.11.
- If you are using Drupal 10.3, update to Drupal 10.3.9.
All versions of Drupal 10 prior to 10.2 are end-of-life and do not receive security coverage. (Drupal 8 and Drupal 9 have both reached end-of-life.)
Reported By:- Drew Webber of the Drupal Security Team
- Drew Webber of the Drupal Security Team
- Fabian Franz
- Juraj Nemec of the Drupal Security Team
- Lee Rowlands of the Drupal Security Team
- Dave Long of the Drupal Security Team
- Alex Pott of the Drupal Security Team
- Juraj Nemec of the Drupal Security Team
- Benji Fisher of the Drupal Security Team
- xjm of the Drupal Security Team
Neue Kommentare
vor 7 Stunden 1 Minute
vor 11 Stunden 9 Minuten
vor 17 Stunden 29 Minuten
vor 1 Tag 11 Stunden
vor 1 Tag 13 Stunden
vor 1 Tag 14 Stunden
vor 1 Tag 17 Stunden
vor 1 Tag 18 Stunden
vor 2 Tagen 2 Stunden
vor 2 Tagen 10 Stunden