View online: https://www.drupal.org/sa-contrib-2025-008
Project: Matomo Analytics [1]
Date: 2025-January-29
Security risk: *Moderately critical* 11 ∕ 25
AC:Complex/A:None/CI:None/II:Some/E:Theoretical/TD:Default [2]
Vulnerability: Cross site request forgery
Affected versions: <1.24.0
Description:
This module enables you to add the Matomo web statistics tracking system to
your website.
The Matomo Analytics Tag Manager sub-module allows you to add one or more
Matomo tag containers on your website.
The module does not protect against Cross Site Request Forgeries on routes to
enable or disable containers.
This vulnerability is mitigated by the fact that:
* The website needs to have the submodule "Matomo Analytics Tag Manager"
enabled.
* An attacker must know the machine name of the container.
Solution:
Install the latest version:
* If you use the Matomo Analytics module 8.x-1.23 and below, upgrade to
Matomo Analytics 8.x-1.24 [3]
Reported By:
* Ivo Van Geertruyen [4] of the Drupal Security Team
Fixed By:
* Ivo Van Geertruyen [5] of the Drupal Security Team
* Florent Torregrosa [6]
Coordinated By:
* Ivo Van Geertruyen [7] of the Drupal Security Team
[1] https://www.drupal.org/project/matomo
[2] https://www.drupal.org/security-team/risk-levels
[3] https://www.drupal.org/project/matomo/releases/8.x-1.24
[4] https://www.drupal.org/user/383424
[5] https://www.drupal.org/user/383424
[6] https://www.drupal.org/user/2388214
[7] https://www.drupal.org/user/383424
View online: https://www.drupal.org/sa-contrib-2025-004
Project: AI (Artificial Intelligence) [1]
Date: 2025-January-22
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: <1.0.3
Description:
The AI logging sub-module enables you to log AI requests and responses for
debugging and auditing purposes.
The module doesn't sufficiently check for access to view the preview listing
of the logs. Full log details are correctly protected, and API keys are never
logged.
This vulnerability is mitigated by the fact that it only affects sites using
the AI Logging sub-module with 'Log requests' enabled in the AI Logging
configuration page.
Solution:
Install the latest version:
* If you use AI 1.x, upgrade to AI 1.0.3 [3].
An update hook will update the view to use the view ai log permission. If you
use version controlled configuration, remember to capture this.
(or) Disable the AI Logging module.
(or) Manually update the ai_logs view's access check to use the view ai log
permission.
Reported By:
* Mingsong [4]
Fixed By:
* Scott Euser [5]
* Marcus Johansson [6]
* Andrew Belcher [7]
Coordinated By:
* Greg Knaddison [8] of the Drupal Security Team
* Juraj Nemec [9] of the Drupal Security Team
* Dave Long [10] of the Drupal Security Team
[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.3
[4] https://www.drupal.org/user/2986445
[5] https://www.drupal.org/user/3267594
[6] https://www.drupal.org/user/385947
[7] https://www.drupal.org/user/655282
[8] https://www.drupal.org/user/36762
[9] https://www.drupal.org/user/272316
[10] https://www.drupal.org/u/longwave
View online: https://www.drupal.org/sa-contrib-2025-003
Project: AI (Artificial Intelligence) [1]
Date: 2025-January-15
Security risk: *Critical* 15 ∕ 25
AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:Default [2]
Vulnerability: Cross Site Request Forgery
Affected versions: >1.0.0 <1.0.2
Description:
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.
Solution:
Install the latest version:
* If you use the AI module, upgrade to AI 1.0.2 [3]
If you cannot update, you can can uninstall the AI Chatbot sub-module.
Reported By:
* Marcus Johansson [4]
Fixed By:
* Marcus Johansson [5]
* Michal Gow [6]
* Kevin Quillen [7]
* Andrew Belcher [8]
Coordinated By:
* Greg Knaddison [9] of the Drupal Security Team
* Drew Webber [10] of the Drupal Security Team
* Juraj Nemec [11] of the Drupal Security Team
[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.2
[4] https://www.drupal.org/user/385947
[5] https://www.drupal.org/user/385947
[6] https://www.drupal.org/user/3065779
[7] https://www.drupal.org/user/317279
[8] https://www.drupal.org/user/655282
[9] https://www.drupal.org/user/36762
[10] https://www.drupal.org/u/mcdruid
[11] https://www.drupal.org//www.drupal.org/u/poker10