September 2025 - Security-news

Reverse Proxy Header - Less critical - Access bypass - SA-CONTRIB-2025-111
by security-news＠drupal.org 24 Sep '25

24 Sep '25

View online: https://www.drupal.org/sa-contrib-2025-111 Project: Reverse Proxy Header [1] Date: 2025-September-24 Security risk: *Less critical* 8 ∕ 25 AC:Basic/A:None/CI:None/II:None/E:Theoretical/TD:Uncommon [2] Vulnerability: Access bypass Affected versions: <1.1.2 CVE IDs: CVE-2025-10929 Description: This module allows you to specify an HTTP header name to determine the client's IP address. The module doesn't sufficiently handle all cases under the scenario if Drupal Core settings $settings['reverse_proxy'] is set to TRUE and $settings['reverse_proxy_addresses'] is configured. This vulnerability allows an attacker to spoof a request IP address (as Drupal sees it), potentially bypassing a variety of controls. Solution: To resolve this issue, sites must both upgrade and confirm their settings. Install the latest 1.1.2 version. [3] Check your settings: - $settings['reverse_proxy'] (Drupal Core setting); - $settings['reverse_proxy_addresses'] (Drupal Core setting); - $settings['reverse_proxy_header'] (this module setting); - $settings['reverse_proxy_header_trusted_addresses_ignore'] (this module setting introduced in this release). This security release does not affect your Drupal instance if: - or $settings['reverse_proxy'] is not set or set to FALSE; - or $settings['reverse_proxy_header'] is not set or set to FALSE; - or $settings['reverse_proxy_addresses'] is not set or set to an empty array. This security release may affect your Drupal instance if: - and $settings['reverse_proxy'] is set to TRUE; - and $settings['reverse_proxy_header'] is set; - and $settings['reverse_proxy_addresses'] is configured. If your configuration meets all three criteria simultaneously, you need to verify how Drupal determines the client IP address. *How to verify:* It can be checked by sending a request from a non-trusted proxy/server like: curl -I -H "X-REVERSE-PROXY-HEADER-NAME:8.8.8.8" your-hostname/some-path` If Drupal detects the client IP address (for example, at the dblog report), everything works as expected. If Drupal detects the client IP address as 8.8.8.8, you may need to check your $settings['reverse_proxy_addresses'] and/or review the documentation in the README file about $settings['reverse_proxy_header_trusted_addresses_ignore']. *Reccomendation:* Although it is not required to have $settings['reverse_proxy_addresses'] (Drupal Core setting) configured, it's always preferred to do so to improve security. Reported By: * Pierre Rudloff (prudloff) [4] provisional member of the Drupal Security Team Fixed By: * Bohdan Artemchuk (bohart) [5] * Drew Webber (mcdruid) [6] of the Drupal Security Team * Pierre Rudloff (prudloff) [7] provisional member of the Drupal Security Team Coordinated By: * Greg Knaddison (greggles) [8] of the Drupal Security Team * Juraj Nemec (poker10) [9] of the Drupal Security Team * Pierre Rudloff (prudloff) [10] provisional member of the Drupal Security Team ------------------------------------------------------------------------------ Contribution record [11] [1] https://www.drupal.org/project/reverse_proxy_header [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/reverse_proxy_header/releases/1.1.2 [4] https://www.drupal.org/u/prudloff [5] https://www.drupal.org/u/bohart [6] https://www.drupal.org/u/mcdruid [7] https://www.drupal.org/u/prudloff [8] https://www.drupal.org/u/greggles [9] https://www.drupal.org/u/poker10 [10] https://www.drupal.org/u/prudloff [11] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Currency - Moderately critical - Cross Site Request Forgery - SA-CONTRIB-2025-110
by security-news＠drupal.org 24 Sep '25

24 Sep '25

View online: https://www.drupal.org/sa-contrib-2025-110 Project: Currency [1] Date: 2025-September-24 Security risk: *Moderately critical* 13 ∕ 25 AC:Basic/A:None/CI:None/II:Some/E:Theoretical/TD:All [2] Vulnerability: Cross Site Request Forgery Affected versions: <3.5.0 CVE IDs: CVE-2025-10930 Description: This module allows you to use different currencies on your website and do currency conversion. The module doesn't sufficiently protect routes used to enable and disable currencies from Cross-Site Request Forgery (CSRF) attacks, potentially allowing an attacker to trick an admin into changing settings. Solution: Install the latest version: * If you use the Currency module for Drupal, upgrade to Currency 8.x-3.5 [3] Reported By: * Juraj Nemec (poker10) [4] of the Drupal Security Team Fixed By: * Sascha Grossenbacher (berdir) [5] * Pieter Frenssen (pfrenssen) [6] Coordinated By: * Juraj Nemec (poker10) [7] of the Drupal Security Team ------------------------------------------------------------------------------ Contribution record [8] [1] https://www.drupal.org/project/currency [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/currency/releases/8.x-3.5 [4] https://www.drupal.org/u/poker10 [5] https://www.drupal.org/u/berdir [6] https://www.drupal.org/u/pfrenssen [7] https://www.drupal.org/u/poker10 [8] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Umami Analytics - Moderately critical - Cross Site Scripting - SA-CONTRIB-2025-109
by security-news＠drupal.org 24 Sep '25

24 Sep '25

View online: https://www.drupal.org/sa-contrib-2025-109 Project: Umami Analytics [1] Date: 2025-September-24 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-2025-10931 Description: This module enables you to add Umami Analytics web statistics tracking system to your website. The "administer umami analytics" permission allows inserting an arbitrary JavaScript file on every page. While this is an expected feature, the permission lacks the "restrict access" flag, which should alert administrators that this permission is potentially dangerous and can lead to cross-site scripting (XSS) vulnerabilities. This vulnerability is mitigated by the fact that an attacker must have a role with the permission “administer umami analytics”. Solution: Install the latest version: * If you use the Umami Analytics module upgrade to Umami Analytics 1.0.1 [3] or 2.0.-beta3 [4] Sites are encouraged to review which roles have that permission and which users have that role, to ensure that only trusted users have that permission. Reported By: * Pierre Rudloff (prudloff) [5] Fixed By: * Ivica Puljic (pivica) [6] Coordinated By: * Damien McKenna (damienmckenna) [7] of the Drupal Security Team * Juraj Nemec (poker10) [8] of the Drupal Security Team * Pierre Rudloff (prudloff) [9] provisional member of Drupal Security Team ------------------------------------------------------------------------------ Contribution record [10] [1] https://www.drupal.org/project/umami_analytics [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/umami_analytics/releases/1.0.1 [4] https://www.drupal.org/project/umami_analytics/releases/2.0.0-beta3 [5] https://www.drupal.org/u/prudloff [6] https://www.drupal.org/u/pivica [7] https://www.drupal.org/u/damienmckenna [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

Access code - Moderately critical - Access bypass - SA-CONTRIB-2025-108
by security-news＠drupal.org 24 Sep '25

24 Sep '25

View online: https://www.drupal.org/sa-contrib-2025-108 Project: Access code [1] Date: 2025-September-24 Security risk: *Moderately critical* 14 ∕ 25 AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2] Vulnerability: Access bypass Affected versions: <2.0.5 CVE IDs: CVE-2025-10928 Description: This module enables users to sign in with an access code instead of entering user names and passwords. When users are allowed to pick their own access codes, they can guess other users' access codes based on the fact that access codes need to be unique and the system warns if the code of their choice is taken. This vulnerability is mitigated by the fact that an attacker must have a role with the "change own access code" permission. Solution: Install the latest version: * If you use access_code module for Drupal, upgrade to access_code 2.0.5 [3] Reported By: * Pierre Rudloff (prudloff) [4] Fixed By: * Gergely Lekli (glekli) [5] * Pierre Rudloff (prudloff) [6] Coordinated By: * Greg Knaddison (greggles) [7] of the Drupal Security Team * Pierre Rudloff (prudloff) [8] provisional member of the Drupal Security Team ------------------------------------------------------------------------------ Contribution record [9] [1] https://www.drupal.org/project/access_code [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/access_code/releases/2.0.5 [4] https://www.drupal.org/u/prudloff [5] https://www.drupal.org/u/glekli [6] https://www.drupal.org/u/prudloff [7] https://www.drupal.org/u/greggles [8] https://www.drupal.org/u/prudloff [9] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Plausible tracking - Moderately critical - Cross Site Scripting - SA-CONTRIB-2025-107
by security-news＠drupal.org 24 Sep '25

24 Sep '25

View online: https://www.drupal.org/sa-contrib-2025-107 Project: Plausible tracking [1] Date: 2025-September-24 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.2 CVE IDs: CVE-2025-10927 Description: This module integrates Plausible Analytics on a site. The module did not properly filter output in certain cases. This vulnerability is mitigated by the fact that an attacker must have permission to add raw HTML to the website, such as an unfiltered WYSIWYG field on a public-facing comment. Solution: Install the latest version: * If you use the Plausible Analytics module for Drupal, upgrade to Plausible Analytics v1.0.2 [3] Reported By: * Pierre Rudloff (prudloff) [4] Fixed By: * Pierre Rudloff (prudloff) [5] * Benjamin Rasmussen (ras-ben) [6] Coordinated By: * Damien McKenna (damienmckenna) [7] of the Drupal Security Team ------------------------------------------------------------------------------ Contribution record [8] [1] https://www.drupal.org/project/plausible_tracking [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/plausible_tracking/releases/1.0.2 [4] https://www.drupal.org/u/prudloff [5] https://www.drupal.org/u/prudloff [6] https://www.drupal.org/u/ras-ben [7] https://www.drupal.org/u/damienmckenna [8] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

JSON Field - Critical - Cross Site Scripting - SA-CONTRIB-2025-106
by security-news＠drupal.org 24 Sep '25

24 Sep '25

View online: https://www.drupal.org/sa-contrib-2025-106 Project: JSON Field [1] Date: 2025-September-24 Security risk: *Critical* 15 ∕ 25 AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:Default [2] Vulnerability: Cross Site Scripting Affected versions: <1.5 CVE IDs: CVE-2025-10926 Description: This module enables you to store and display JSON data using optional 3rd party libraries. The module doesn't sufficiently filter data using some of the included field formatters leading to a Cross-site Scripting (XSS) vulnerability. Solution: Install the latest version: * If you use the JSON Field module for Drupal 8.x, upgrade to JSON Field 8.x-1.5 [3]. Reported By: * Ivan (chi) [4] Fixed By: * Ivan (chi) [5] * Damien McKenna (damienmckenna) [6] 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 ------------------------------------------------------------------------------ Contribution record [9] [1] https://www.drupal.org/project/json_field [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/json_field/releases/8.x-1.5 [4] https://www.drupal.org/u/chi [5] https://www.drupal.org/u/chi [6] https://www.drupal.org/u/damienmckenna [7] https://www.drupal.org/u/damienmckenna [8] https://www.drupal.org/u/greggles [9] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Third-Party Libraries and Supply Chains - PSA-2025-09-17
by security-news＠drupal.org 17 Sep '25

17 Sep '25

View online: https://www.drupal.org/psa-2025-09-17 Date: 2025-September-17 Description: .... Supply-chain attack via maintainer account takeover NPM [1] packages have been targeted in maintainer account takeover attacks. Attackers have deployed an automatic credential scanning tool. The scanning tool tries to find secret keys that may have been published to public systems like build automation and continuous integration (CI) systems and sends such credentials back to the attacker. From there, the vulnerable NPM packages are downloaded, modified to insert a trojan-like script bundle, and then republished. These maliciously modified packages can then be used to exploit any application that has installed these packages. Coverage and advice on remediation: * The Hacker News - 40 NPM Packages Compromised [2] * Socket.dev - Supply Chain Attack [3] * Aikido - S1ngularity/nx attackers strike again [4] * Aikido - npm debug and chalk packages compromised [5] * Wiz.io - Shai-Halud npm supply chain attack [6] While this attack has targeted NPM packages, the same strategy could be used to exploit other packages as well. .... Managing supply-chain security Website owners should actively manage their dependencies, potentially leveraging a Software Bill of Materials (SBOM) or scanner services. Other relevant tools include CSP [7] and SRI [8]. It is the policy of the Drupal Security Team that site owners are responsible for monitoring and maintaining the security of third-party libraries and any non-Drupal components of the stack. In rare cases, the Drupal Security Team will post an informational public service announcement [9] (PSA) such as this one, but the remit of the Drupal Security Team remains limited to code hosted on Drupal.org’s systems. Previous PSAs on third-party code in the Drupal ecosystem include: * External libraries and plugins - PSA-2011-002 [10] * Various Third-Party Vulnerabilities - PSA-2019-09-04 [11] * Third-Party Libraries and Supply Chains - PSA-2024-06-26 [12] .... Impact to the Drupal project itself Drupal's infrastructure maintainers, the Drupal Security Team, and Drupal core maintainers have received tips about this situation from several sources. Individuals in those groups have evaluated their exposure and we believe the Drupal project itself is not affected by this issue. If you have information about concerns that Drupal is affected please reach out to us [13]. /This post is likely to be be updated as the situation evolves and more information is available./ Reported By: * nicxvan [14] Coordinated By: * Greg Knaddison (greggles) [15] of the Drupal Security Team * Tim Hestenes Lehnen (hestenet) [16] * Dave Long (longwave) [17] of the Drupal Security Team * Drew Webber (mcdruid) [18] of the Drupal Security Team * Jess (xjm) [19] of the Drupal Security Team * cilefen [20] of the Drupal Security Team ------------------------------------------------------------------------------ Contribution record [21] [1] https://www.npmjs.com [2] https://thehackernews.com/2025/09/40-npm-packages-compromised-in-supply.html [3] https://socket.dev/blog/ongoing-supply-chain-attack-targets-crowdstrike-npm… [4] https://www.aikido.dev/blog/s1ngularity-nx-attackers-strike-again [5] https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised [6] https://www.wiz.io/blog/shai-hulud-npm-supply-chain-attack [7] https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP [8] https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity [9] https://www.drupal.org/security/psa [10] https://www.drupal.org/node/1189632 [11] https://www.drupal.org/psa-2019-09-04 [12] https://www.drupal.org/psa-2024-06-26 [13] https://www.drupal.org/docs/develop/issues/issue-procedures-and-etiquette/r… [14] https://www.drupal.org/u/nicxvan [15] https://www.drupal.org/u/greggles [16] https://www.drupal.org/u/hestenet [17] https://www.drupal.org/u/longwave [18] https://www.drupal.org/u/mcdruid [19] https://www.drupal.org/u/xjm [20] https://www.drupal.org/u/cilefen [21] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Acquia DAM - Moderately critical - Access bypass, Information Disclosure - SA-CONTRIB-2025-105
by security-news＠drupal.org 03 Sep '25

03 Sep '25

View online: https://www.drupal.org/sa-contrib-2025-105 Project: Acquia DAM [1] Date: 2025-September-03 Security risk: *Moderately critical* 12 ∕ 25 AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] Vulnerability: Access bypass, Information Disclosure Affected versions: <1.1.5 CVE IDs: CVE-2025-9954 Description: This module enables you to connect a Drupal site to the Acquia DAM service, which syncs media from the third party service to the site. The module doesn't sufficiently validate authorization to a list of DAM assets currently synced to the website creating an access bypass vulnerability. This vulnerability is mitigated by the fact that it only impacts sites where users having the “view media” permission accessing any DAM asset is undesirable. *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 which will automatically reset three views to have permission-based access control based on the "access media overview" permission. If you have modified the view access in some other way you will need to redo that modification after upgrading the module. * If you use the acquia_dam module for Drupal 8.x, upgrade to acquia_dam 1.1.5 [5] Sites that cannot update to this code can mitigate the issue by modifying three views to be restricted to that permission: Acquia DAM Asset Library, Acquia DAM links, DAM Content Overview. Reported By: * Brandon Goodwin (bgoodie) [6] * Chris Burge (chris burge) [7] * Todd Woofenden (toddwoof) [8] Fixed By: * Chris Burge (chris burge) [9] * Damien McKenna (damienmckenna) [10] of the Drupal Security Team * Jakob P (japerry) [11] * Todd Woofenden (toddwoof) [12] Coordinated By: * cilefen (cilefen) [13] of the Drupal Security Team * Greg Knaddison (greggles) [14] of the Drupal Security Team * Cathy Theys (yesct) [15] of the Drupal Security Team ------------------------------------------------------------------------------ Contribution record [16] [1] https://www.drupal.org/project/acquia_dam [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/acquia_dam/releases/1.1.5 [6] https://www.drupal.org/u/bgoodie [7] https://www.drupal.org/u/chris-burge [8] https://www.drupal.org/u/toddwoof [9] https://www.drupal.org/u/chris-burge [10] https://www.drupal.org/u/damienmckenna [11] https://www.drupal.org/u/japerry [12] https://www.drupal.org/u/toddwoof [13] https://www.drupal.org/u/cilefen [14] https://www.drupal.org/u/greggles [15] https://www.drupal.org/u/yesct [16] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0