Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Network-reachable object injection needs a low-privileged authenticated account (PR:L), no interaction, yielding high confidentiality and integrity impact but no availability effect.
Primary rating from Vendor (drupal).
CVSS VectorVendor: drupal
Lifecycle Timeline
9DescriptionCVE.org
Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in Drupal Tealium iQ Tag Management allows Object Injection. This issue affects Tealium iQ Tag Management versions: from 0.0.0 to 2.4.0.
AnalysisAI
Object injection in the Drupal Tealium iQ Tag Management contributed module (versions before 2.4.0) lets authenticated attackers manipulate dynamically-determined object attributes to compromise data confidentiality and integrity. Because the CVSS vector (AV:N/AC:L/PR:L) indicates a low-privileged authenticated user over the network, any user with a foothold on the site can potentially abuse the flaw; there is no public exploit identified at time of analysis and the EPSS probability is low (0.42%). Drupal has published advisory SA-CONTRIB-2026-064 and released a fixed version.
Technical ContextAI
Tealium iQ Tag Management is a Drupal contributed module that integrates the Tealium iQ enterprise tag-management platform (used to deploy marketing/analytics JavaScript tags) into Drupal sites. The root cause is CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes), commonly known as object injection or mass-assignment/property-oriented injection. This class of flaw occurs when untrusted input is used to set or overwrite object properties or is deserialized into a PHP object without restricting which attributes can be modified, allowing an attacker to influence application state, inject unexpected object properties, or trigger PHP object-injection gadget chains. The CPE cpe:2.3:a:drupal:tealium_iq_tag_management confirms the affected component is the Drupal application-layer module rather than the Tealium SaaS platform itself.
RemediationAI
Upgrade the Tealium iQ Tag Management module to version 2.4.0 or later, which is the first release outside the affected range and corresponds to the vendor's patch (Patch: Available from vendor; Drupal advisory SA-CONTRIB-2026-064 at https://www.drupal.org/sa-contrib-2026-064). This is the primary and recommended fix. If you cannot upgrade immediately, reduce exposure by tightening the Drupal permission model so that only fully trusted roles can reach the module's functionality - since exploitation requires an authenticated low-privileged account (PR:L), removing or restricting the relevant module permissions and auditing/limiting account creation and untrusted user roles meaningfully shrinks the attack surface, at the cost of restricting legitimate tag-management workflows. As a further compensating control, place the affected admin/configuration endpoints behind additional access controls (e.g., IP allowlisting or a VPN for the Drupal admin area) and review logs for anomalous submissions to the module's forms; note this may inconvenience remote administrators. Uninstalling the module entirely is the most complete mitigation if the Tealium integration is not in active use.
Same technique Code Injection
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-43068
GHSA-7cjh-fc62-8rrg